squire

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

No annotations provided, so description carries full disclosure burden. It explains conceptual behavior well (discovery surface) but omits technical details like return format (text vs structured), caching behavior, or output length limits. Adequate for a low-risk help tool but lacks richness expected when annotations are absent.

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 sentences with zero waste. First sentence defines functionality; second sentence establishes workflow position ('canonical discovery surface...'). Every word earns its place—efficiently front-loaded with no redundancy.

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?

Appropriately complete given low complexity (1 optional string param) and lack of output schema. Sufficiently explains the tool's role in the ecosystem. Minor gap: does not describe output format (human-readable text? JSON?) which would help given no output schema exists.

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 100% description coverage ('Optional command path, such as verify or quantum simulate'). With high schema coverage, baseline is 3. The description adds minimal semantic detail beyond the schema, merely reinforcing the 'help for a specific command' use case.

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?

Explicitly states what the tool does: 'Show the top-level Squire command catalog or help for a specific command.' Uses specific verb 'Show' with clear resources (catalog/help). References sibling commands 'verify' and 'quantum simulate' in the description, distinguishing this discovery tool from the operational siblings.

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?

Strong contextual guidance: 'This is the canonical discovery surface for humans and agents before choosing a command.' Clearly positions when to use it (before choosing other commands). Lacks explicit 'when not to use' guidance or specific alternative comparisons, falling short of a perfect 5.

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