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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable behavioral detail: it routes across 5,721 tools, fills arguments, returns structured answers with stable pipeworx:// URIs, and is described as one fast call. This exceeds the minimum needed beyond annotations.

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 efficient: it front-loads the key directive, then supplies triggers, examples, and explicit escalation paths. Every sentence adds decision-relevant information, and the formatting makes scanning easy.

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, route-style tool with no output schema, the description explains what the answer will look like (structured, with citation URIs), when to use it, and how it relates to siblings. The examples and coverage statement give an agent enough context to call it correctly even with the massive tool surface area.

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% and the input schema clearly documents the single required 'question' field plus aliases. The description does not add parameter-level semantics beyond saying it 'fills arguments', but it doesn't need to; the schema carries that burden fully.

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 role — a default router that answers factual questions from authoritative structured sources with citation URIs — and clearly distinguishes it from web search and from sibling tools like ask_pipeworx_grounded and deep_research. Concrete domain list and examples make the purpose immediately actionable.

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 says 'PREFER OVER WEB SEARCH', provides trigger phrases ('what is', 'look up', 'find'), and gives escalation guidance: use ask_pipeworx_grounded for hallucination-resistant answers and deep_research for broad/multi-part queries. This leaves little ambiguity about when to invoke this tool versus alternatives.

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