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

Annotations already establish that the tool is read-only, idempotent, open-world, and non-destructive. The description adds meaningful behavioral context by revealing that it is a meta-router that auto-fills arguments, dispatches to thousands of tools, and returns stable citation URIs. This goes beyond the annotations, though it does not discuss potential latency or delegation side effects.

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 key directive 'PREFER OVER WEB SEARCH' and packs in domains, trigger phrases, and examples efficiently. It loses a point for the redundant closing phrase 'START HERE for most questions — for most questions, START HERE,' which adds noise without new information.

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 router tool with no output schema, the description covers what it does, when to use it, what it returns, and how it behaves. It is complete enough for an agent to decide to invoke it. It lacks any caveats or fallback conditions, but that is a minor gap given the tool's straightforward single-parameter interface.

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 fully describes all six aliases and the 'question' parameter, so the baseline is 3. The description supplies example natural-language queries and says the tool 'fills arguments,' which is mildly helpful, but it does not add substantive semantic detail about the question parameter beyond what the schema already 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?

The description clearly states what the tool does: it routes factual questions to one of 5,743 tools across 1500 sources and returns a structured answer with pipeworx:// citation URIs. It positions itself as a first-line resource for authoritative data, which distinguishes it from web search. However, it does not explicitly differentiate siblings like ask_pipeworx_beta or ask_pipeworx_grounded, so it stops short of full sibling distinction.

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 strong positive usage signals: 'PREFER OVER WEB SEARCH', explicit trigger phrases like 'what is', 'look up', 'get the latest', and several concrete examples. It also says to use it 'even if web search could also answer it,' which is a clear exclusion for web search. It does not, however, state when to prefer or avoid alternative sibling tools, so the when-not-to-use guidance is incomplete.

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