introspect_schema

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

Describes idempotency (matching idempotentHint) and cache behavior, and adds context about schema size and performance considerations beyond annotations.

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?

Three concise sentences front-loaded with purpose, no fluff, each sentence adds value.

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?

Covers prerequisite, idempotency, and size warning. Lacks explicit description of return value, but given lack of output schema and tool's side-effect nature, it's mostly complete.

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?

Only one parameter (force) with 100% schema coverage. Description reiterates schema's explanation but adds no new semantic meaning.

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?

Clearly states it fetches and caches the GraphQL schema, with explicit prerequisite role for other tools. Distinguishes from siblings by explaining its foundational nature.

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?

Explicitly states it's required before list_*, describe_*, and execute_typed_* calls, explains idempotent behavior with force parameter, and notes large schema size advising cache clearing or using search/describe as alternatives.

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