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

Annotations already establish read-only, idempotent, open-world behavior. The description adds useful behavioral context beyond annotations: it routes questions, fills arguments automatically, returns stable pipeworx:// citation URIs, works on every tier, and makes one fast call. This goes beyond what the structured annotations alone provide.

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?

Front-loaded with the key 'PREFER OVER WEB SEARCH' directive and organized into usage, examples, and escalation paths. It is long, but the breadth of a 5,724-tool router justifies most of the content; a few marketing-style phrases like 'works on every tier' add marginal value.

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?

Because there is no output schema, the description correctly explains the return value: a structured answer with stable pipeworx:// citation URIs. It also covers supported domains, example queries, and when to use sibling tools. Minor gaps around failure behavior, rate limits, or unsupported question types keep it from being fully complete.

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% and the parameter descriptions already document the question field plus aliases. The tool description adds value through concrete example queries and phrasing guidance ('what is', 'look up', 'get the latest'), but it does not add new syntax or parameter-specific mechanics beyond what the schema provides.

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?

Clearly states it is a routing question-answering tool that selects among 5,724 tools across verified sources and returns structured answers with citation URIs. It also differentiates itself from ask_pipeworx_grounded and deep_research by naming those alternatives explicitly.

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?

Provides explicit when-to-use guidance: prefer over web search, start here for most factual questions, and step up to ask_pipeworx_grounded for hallucination-resistant single answers or deep_research for broad/multi-part questions. It also addresses breaking-news cases, leaving little ambiguity about selection.

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