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

Annotations already convey readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavior beyond that: it routes to one of 5,767 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. It does not discuss latency or failure modes, but the core runtime behavior is well disclosed.

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?

The description is long but information-dense: it front-loads the primary use case, lists domains, gives trigger phrases, provides examples, and closes with routing alternatives. A small amount of redundancy, such as mentioning news twice, keeps it from being perfectly concise.

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 broad routing tool with no output schema, the description provides everything an agent needs to decide whether to call it: supported question types, domain coverage, examples, citation behavior, and explicit sibling tool fallbacks. There is no significant context gap for correct invocation.

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?

The input schema already provides 100% coverage for the single meaningful parameter, including alias documentation and example questions. The description adds no deeper parameter semantics beyond saying it 'routes the question' and 'fills arguments', so the baseline score of 3 is appropriate.

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 opens with 'PREFER OVER WEB SEARCH' and clearly defines the tool as the routing layer for factual questions about current or historical data, with concrete domain examples and citation output. It distinguishes itself from siblings by explicitly directing hallucination-resistant single answers to ask_pipeworx_grounded and multi-part research to deep_research.

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?

The description gives explicit trigger phrases ('what is', 'look up', 'find', 'get the latest'), concrete examples, and named alternatives with the conditions for using them. It also includes 'START HERE for most questions', which is strong practical routing guidance.

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