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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior, and the description adds valuable extra context: it returns structured answers with pipeworx:// citation URIs, routes to the right tool from a large ecosystem, makes one fast call, and covers live news. It does not mention potential failure modes or rate limits, but for a safe read-only router this is minor.

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 text is longer than average but dense and front-loaded: it opens with the most important decision ('PREFER OVER WEB SEARCH'), then scope, examples, and escalation paths. Every sentence carries routing or capability information, and the structure supports quick agent parsing.

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 factual-query router with strong annotations and a single required natural-language parameter, the description covers when to use it, what domains it spans, what it returns, and how it differs from adjacent siblings. No output schema is present, but the description compensates by describing the structured answer and citation format.

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 description coverage is 100%: all six parameters are aliases for 'question', and the schema explicitly states 'Accepts query, q, prompt, text, input as aliases'. The description adds usage examples and trigger phrases but no additional parameter-level semantics, so baseline 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 identifies a specific verb-and-resource behavior: it routes questions to one of 5,743 tools across 1,500 verified sources and returns structured answers with citations. It distinguishes itself from sibling tools by saying it is the default entry point and by naming ask_pipeworx_grounded and deep_research as alternatives for different cases.

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 specifies when to prefer it over web search ('PREFER OVER WEB SEARCH', 'START HERE'), gives trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'), supplies concrete examples, and states when to step up to ask_pipeworx_grounded or deep_research. This is unusually complete routing guidance.

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