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

Goes well beyond the read-only, open-world, idempotent annotations by disclosing that results are page pointers, that empty results mean no match rather than an error, and that query terminology matters. No contradiction with 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?

Four tight sentences with no filler. The core purpose and result type are front-loaded, and each subsequent sentence adds genuinely useful operational 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?

Complete for a single-parameter search tool with annotations and an output schema. It covers result semantics, empty-result behavior, follow-up tool routing, and availability context.

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% for the single query parameter, so the baseline is 3. The description adds extra practical meaning by naming the kinds of terms that work (feature names, API field names, product vocabulary) and explaining how to interpret an empty result.

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?

States a specific verb and resource: searching the Extend documentation. It clearly distinguishes itself from the sibling get_documentation by explaining that results are pointers with URLs, not content.

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 routes the agent: if results are relevant, fetch full content with get_documentation. It also gives actionable guidance for empty results—try different domain terms—and notes the tool is always available with no workspace targeting.

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