Schema Design: Be explicit with descriptions

Provide comprehensive context in descriptions, including clear definitions. Avoid team-specific acronyms, describe all enum values, and link to authoritative sources where relevant.

Rationale: Future developers should be able to understand schema elements using only the provided documentation. Include what a concept is, why it matters, where to find additional information, and concrete examples for enum options.

Start by locating the schema definitions in the graphql.github.io codebase and review how their descriptions are currently written. Done means descriptions provide context and clear definitions, avoid team-specific acronyms, document every enum value, link authoritative sources where relevant, and include purpose, additional-information pointers, and concrete examples.

Vom Indexierungsmodell aus dem Issue-Text verfasst.