It's also not clear from the other side. Do you give a lot of guidance, so the intern becomes reliant on always having someone telling them what to do exactly on the micro level? Or let them work it out slowly, and during that process get familiar with the systems more closely? I find that having a clear task to solve actually gets me more of an understanding of how everything works, than reading a top-down documentation where I don't have any context of "why".

Also interns can differ a lot. They can need different levels of guidance and can come with widely different levels of prior experience, even in unrelated debugging and troubleshooting like fixing network ports for LAN gaming or whatever kids these days might be doing. Setting up VPN to evade geoblocking or whatever. Others may have no idea what to even do. And those who can do it may take widely different time.

I think an internship is, in fact, a good place to learn these meta-lessons too. You ask for some guidance, then you see it was maybe too much. Another time you don't and spend a lot of time, and have your supervising engineer say "oh I could have told you XYZ very quickly", then you update and recalibrate. There is no single short message that can convey this. That's why experience is valuable.