How do you document a schematic so the next engineer isn't lost?

I inherited a 12-sheet schematic with no design notes, and reverse-engineering the design intent took weeks. I want to do better on my current project. Beyond net labels, what documentation practices actually help the next engineer — design rationale notes, block diagrams, a separate theory-of-operation doc?