Umm, GraphQL is a reflective API-- use 'introspection':
https://graphql.org/learn/introspection/
Introspection is not valid in place of documentation.
When it comes to APIs if you're eschewing documentation it's because (I hope) you are trying to minimize support costs and thus devs using the API won't have someone to ask questions of so those edge cases become mysterious and assumptions are made that may be wrong.
If you're designing an API that serves up items that may be on sale how would you name fields so that the price and possibly sale discount are unambiguous to read?