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

Annotations already provide the safety profile (readOnly, openWorld, idempotent, non-destructive). The description adds behavioral context beyond that: it discloses that the tool automatically routes and fills arguments, handles a broad range of domains, and returns citation URIs. It also hints at limitations by noting when to escalate to grounded or deep_research, which helps set expectations. It does not disclose every operational detail, but the annotations lower the bar and the added context is useful.

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 well-structured: it front-loads the key routing instruction, then explains mechanics, trigger phrases, examples, and alternatives. Every section earns its place, though the extensive domain list and repetition of 'current or historical data' could be trimmed slightly. Overall it is dense but not bloated.

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 complex routing tool with no output schema, the description is nearly complete: it specifies input shape, example queries, when to use it, what it returns, and when to choose alternatives. The main gap is that it does not mention ask_pipeworx_beta as a sibling option, and the return format is only described as 'structured answer with stable pipeworx:// citation URIs' without further detail. Still, an agent has enough to select and 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% and the schema already documents question plus aliases. The description adds value by showing realistic example questions, clarifying that the input is a natural-language request, and stating that the tool fills arguments itself so the user does not need to supply additional parameters. This goes beyond simply restating the schema.

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 a specific verb and resource: it routes a natural-language question to the right tool among 5,743 tools across 1,500 verified sources and returns a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as the 'step up' alternatives, and from web search by explicitly saying to prefer it for authoritative factual data.

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 explicit and rich: it says to prefer this over web search, lists concrete question phrasings and example topics, says 'START HERE for most questions', and gives clear when-not-to-use guidance by pointing to ask_pipeworx_grounded for evidence-grounded answers and deep_research for broad multi-part questions.

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