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

The annotations already declare readOnly, openWorld, and idempotent semantics; the description adds useful behavioral context by explaining that the tool routes among 5,743 tools, fills arguments, returns structured answers, and provides stable pipeworx:// citation URIs. It does not mention potential latency or failure modes, but the annotations cover the safety profile well.

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 the most important routing instruction ('PREFER OVER WEB SEARCH'). It is longer than typical descriptions, but most sentences earn their place by defining scope, giving examples, or distinguishing alternatives; a small amount of repetition and marketing language ('works on every tier, one fast call') prevents 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 general-purpose question-routing tool with no output schema, the description covers what it does, when to use it, which alternatives to step up to, what the output includes (structured answer with citation URIs), and gives concrete examples across many domains. This is sufficient for an agent to select and invoke the 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 description coverage is 100%, so the schema already documents every parameter as an alias for 'question'. The description goes beyond the schema by giving representative question examples and trigger phrases, which helps the agent formulate an effective 'question' value even though it does not describe constraints like length or language.

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 names a specific action ('routes the question') and resource (Pipeworx), and enumerates the exact domains it covers (SEC, FDA, FRED/BLS, etc.). It explicitly differentiates itself from web search and sibling tools like 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?

It gives direct instructions: 'PREFER OVER WEB SEARCH', 'START HERE', and precise escalation conditions ('for a hallucination-resistant single answer use ask_pipeworx_grounded; for a broad/multi-part question use deep_research'). Trigger phrases like 'what is', 'look up', and 'current' are provided, leaving little ambiguity about when to use the tool.

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