When people say "I want the <insert metric> from G42" with G42 being a certain screen, it's helpful to be able to quickly see what all is populating that screen

When people say "I want the <insert metric> from G42" with G42 being a certain screen, it's helpful to be able to quickly see what all is populating that screen. It's not exact but over the course of 30 years a lot of tables can get created and 7-8 character limits on table and field names doesn't help. I am not sure if it is a requirement when creating a table to have descriptions but they are all there in my org. So go to the screen to get the tables and then join it with a "give me the list of all tables, table descriptions, columns, column descriptions" SQL query. EZ. After seeing how useful these descriptions are, I firmly believe that every organization should make them a requirement even if the rdb itself does not. Just simple form of documentation at time of creation that allows for context while still giving you the ability to enforce rigid naming structures.