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

Annotations already declare readOnly/openWorld/idempotent behavior, and the description adds meaningful context beyond them: it routes to a large internal toolset, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and is described as 'one fast call'. This goes beyond what the annotations alone convey, though it does not discuss latency, failure modes, or rate limits.

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 dense and front-loaded with its central directive ('PREFER OVER WEB SEARCH'), and the examples and sibling routing earn their place. It is long, but the length is justified by the tool's role as a default entry point covering many domains; a small amount of redundancy around authoritative data and citations keeps it from a 5.

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-natural-language-parameter tool with safe/idempotent annotations, the description is complete: it covers scope, return format, example inputs, relationship to alternatives, and even handling of breaking news. There is no output schema, but the description compensates by noting the structured answer and citation URIs, leaving an agent with enough to call it 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%, so the schema already documents all parameter aliases and the 'question' property. The description reinforces that the input is a natural-language question and gives examples, but it does not add materially new parameter semantics beyond what the input schema already provides; the baseline 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 uses a specific verb ('routes the question') and resource ('one of 5,724 tools across 1497 verified sources'), and explicitly differentiates from sibling tools like ask_pipeworx_grounded and deep_research. It also names the exact categories of questions it handles, so an agent can clearly recognize when to invoke it.

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?

Usage guidance is unusually explicit: it says to prefer this over web search, gives concrete trigger phrases ('what is', 'look up', 'find', 'get the latest'), provides examples, and states 'START HERE for most questions'. It also names the conditions for stepping up to ask_pipeworx_grounded or deep_research, which fully covers when-not-to-use.

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