MSDN is better than most, but there's still a ton in there in places that has no examples or usage information, no indication of what valid inputs are, no indication of any other external state that could derp things up.

obviously some documentation is better than others, and asking specific questions to fill in the gaps where documentation is unclear is a good thing to do.

however, programming is very much driven by learning how to find the answers to problems on your own. often those answers are in the documentation but not always. sometimes they haven't been answered by anyone before and learning how to extrapolate from documentation to understand the behavior of programs in new situations is a skill that has to be developed.

and of course, ultimately, the final authoritative document on how a program will behave is the code itself. there are times when you have to read source. hopefully those are rare occasions, but being capable of doing it when necessary is yet another skill that needs to be developed. reading through an unfamiliar codebase is difficult and requires practice and experience.

all of these technical reading skills need to be practiced. beginners frequently make the mistake of denying themselves opportunities to practice those skills by simply asking for someone to tell them the answer.

These are skills that develop over a programmers career. And when you have issues like getting a for loop going, or if you can have a for loop in a while loop, then reading the documentation is not going to be very useful. Again, information density and assumed level of programming competence in source documentation won't help if you are trying to figure out fundamental programming issues.

Should people read documentation, of course, but the usefulness of documentation increases with programming ability.