what happens when your column names dont accurately represent what data is being stored (i know i wish it did but it doesnt at my place right now) and its all esoteric knowledge held by our data scientists? my worry is now the guys above will think its answering their question without knowing that its either A. wrong or B. data they may not be able to use for legal reasons on the project they are trying to make.
In the product I work on, there's a Metadata layer that maps user-supplied definitions, notes and commentary onto the raw table descriptions
These are optional but it allows manual override when schema design is poor