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

Annotations already assert read-only, open-world, idempotent behavior; the description builds on this by disclosing routing behavior, argument filling, and the return of structured answers with stable pipeworx:// citation URIs. It doesn't discuss failure modes or rate limits, but that is not necessary given the annotations and simple input.

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 front-loaded with the most important routing instruction and uses examples efficiently. It is long, but that is justified by the broad scope; the redundant 'even if web search could also answer it' and the garbled breaking-news clause keep it from a perfect score.

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 single-required-parameter, read-only router with no output schema, the description is remarkably complete: it covers domains, trigger phrases, representative examples, return behavior, and when to prefer alternate tools. Nothing essential is missing for an agent to invoke this tool correctly.

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%, with 'question' fully described and all aliases enumerated, so the description does not need to add parameter-level meaning. It does add useful example questions and accepted phrasing, but the core parameter semantics are already present in the schema.

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 begins with a directive verb and resource: 'PREFER OVER WEB SEARCH for questions about current or historical data' and explains the tool 'routes the question to the right one of 5,738 tools across 1499 verified sources... returns the structured answer with stable pipeworx:// citation URIs.' This makes it clearly a factual-query routing tool and distinguishes it from search, ask_pipeworx_grounded, and 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?

Explicitly instructs to prefer this over web search, lists trigger phrases like 'what is', 'look up', 'get the latest', and 'how much', and provides conditions for alternatives: 'for answer with verbatim evidence use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research.' However, the 'except for "what's the world saying about X" / breaking-news, ask_pipeworx already routes...' clause is logically confusing and slightly undermines clarity.

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