get_schema

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

Without annotations, the description needs to carry behavioral context. It discloses the output format (SDL), the scope (the collection), and positions it as a prerequisite for non-trivial GraphQL queries. It doesn't discuss auth or rate limits, but for a zero-parameter read-only schema fetch, this is sufficient.

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?

Two short sentences, with the primary statement first and a usage hint second. Every word earns its place, making it appropriately sized and front-loaded.

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?

The tool is simple (no params, no output schema), and the description gives the purpose, output format, and usage context. It fully answers what an agent needs to know to use the tool correctly.

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?

The schema defines zero parameters, so there is nothing to document. Baseline for 0 params is 4; the description adds no conflicting info and correctly focuses on the returned schema.

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?

The description clearly states the tool returns 'The GraphQL schema for the collection, as SDL.' This identifies the resource (GraphQL schema) and format (SDL), and distinguishes it from sibling tools like graphql which executes queries, and search_notes/get_note which handle notes.

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?

It provides an explicit usage context: 'Call this before writing a non-trivial query with the graphql tool.' This tells the agent when to use it, though it does not mention exclusions or alternatives, hence not a 5.

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