search

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds beyond annotations: it specifies the calling convention (top-level query string) and return behavior ('Returns matching operations with parameter schemas and usage examples'). No contradictions.

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, front-loaded with purpose, no redundant words. Every sentence earns its place by providing critical usage and context.

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?

Given complexity as a meta-tool for searching operations, description covers purpose, invocation pattern, and return content. Output schema exists, so return values are documented there. Could mention error handling or pagination but not required for this scope.

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 descriptions are present for both parameters (query and category). The description adds value by clarifying the top-level query format (not inside params) which differs from the nested schema. Despite context indicating 0% schema description coverage, the actual schema includes descriptions, so the description enhances understanding.

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?

Description uses specific verb 'Discover' and resource 'available operations and their parameters'. It clearly differentiates from sibling 'execute' by stating 'Always use this before calling execute to find the correct operation name'. Purpose is unambiguous and distinct.

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 advises 'Always use this before calling execute' and specifies input format: 'Call with a top-level query string (not inside params)'. Full guidance on when and how to use.

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