directus_get_graphql_sdl

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden, yet it omits authentication requirements, schema caching behavior, output format details (raw SDL string vs object), and typical response size. 'Get' implies read-only but lacks specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is appropriately brief, but the '[UNIFIED]' prefix wastes tokens without conveying tool semantics. Front-loading is harmed by this non-semantic tag.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without output schema or annotations, and returning a complex schema format (GraphQL SDL), the description should clarify the return structure. It also fails to explain the 'site' parameter, leaving critical gaps for a single-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% coverage for the 'site' parameter. Description fails to compensate by not mentioning what 'site' represents (URL prefix, project name, or identifier) or providing an example, leaving the parameter effectively undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verb 'Get' and resource 'GraphQL SDL schema', distinguishing it from sibling tools like directus_get_openapi_spec (REST) and directus_get_schema_snapshot (database). However, the '[UNIFIED]' prefix is noise that doesn't aid selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this versus alternatives like directus_get_openapi_spec, or prerequisites like requiring a valid site configuration. No 'when-not' or workflow context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.