Make all the rules you want. Only you can follow your rules.
PC drafting don't follow your rules. They can't read schematics, and they never worked on any electronic anything first hand.
All they want is a netlist, PWB artwork, BOM and auto insert data base. They don't maintain the product.
This is what I learned in 30 years of working on avionics.
It was frustrating, PC drafting fell into "engineering services" organization. They had their own vice-president. And a fundamental rule of large organizations is never say anything bad outside of your organization. So in the 30 years I was there, it never improved. The design quality was left to the engineer, and how tenacious they were in dealing with idiots.
You could leave a list of layout rules, and they were ignored. There were a few designers that knew what they were doing, but you could never get them to work on your board, as they were in demand and everything was a que to get through their hurtle. The organization did everything to prevent engineering having access to the schematic capture tool (EPD), and the board layout tool (VISULA/CR5000).
To try to add to useful input:
Notes for service center technicians that (especially for analog) indicate the signal processing blocks. If you stick build a differential amp, draw it so it looks like a differential amp.
For processor based sch. have a memory map on the processor or memory page.
Layout notes that are released with the schematic are good (for future support by the next cognizant), if they can be excluded from the published version to limit intellectual property info.