List QE blueprints

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

Annotations already provide readOnlyHint and idempotentHint. Description adds valuable context: returns only titles/summaries, is a catalog index, and stage enumerates valid stages. No contradiction with annotations (repeats idempotent).

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 sentences with clear structure: purpose, usage, return format. Every sentence earns its place—no redundancy, front-loaded with primary purpose.

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?

For a simple tool with one optional param and an output schema, the description fully covers what the tool does, what it returns, how to use the parameter, and sets expectations (catalog index, not content). No gaps.

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 coverage is 100%, baseline 3. Description adds extra meaning beyond schema: the note about omitting stage to return the whole catalog (small enough). Also reiterates that stage enumerates valid stages, reinforcing enum usage.

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 uses specific verb+resource ('list QE blueprints') and clearly distinguishes from siblings like 'search_methodology' and 'get_document' by noting it returns a catalog index with titles and summaries, not full instructions.

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 when to use ('find the blueprint that fits a QE task') and what is returned (catalog index). Provides guidance on the stage parameter (omit for full catalog). Missing explicit when-not-to-use or alternatives among siblings, but context is clear.

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