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

With readOnlyHint, openWorldHint, and idempotentHint already set, the safety profile is covered by annotations, and the description adds genuinely useful behavioral context: it auto-fills arguments, dispatches to a large external tool network, and returns structured answers with stable citation URIs. There is no contradiction with the annotations. It stops short of disclosing caveats like latency or what happens when no routed tool can answer a question.

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 its strongest directive and most sections earn their place, but it repeats the 'even if web search could answer it' caveat twice, and 'START HERE' largely duplicates 'PREFER OVER WEB SEARCH'. It also trails off into a garbled, incomplete closing fragment ('...Schema for a broad multi-part question that should fan out across many sources at once'), which undermines an otherwise dense and efficient structure.

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?

Despite having no output schema, the description covers the return contract ('structured answer with stable pipeworx:// citation URIs'), the input contract, scope, and selection criteria, which is strong for a read-only Q&A router. The main gaps are that it does not differentiate the ask_pipeworx_beta and ask_pipeworx_grounded siblings and says nothing about failure modes for unsupported questions.

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%: the single question parameter plus its five aliases are all documented in the schema. The description adds practical color via trigger phrases and six domain-spanning examples, but it contributes no format, length, or query-structuring conventions beyond what the schema already states ('Your question or request in natural language'). The schema does the heavy lifting here.

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 verb and resource: it routes factual questions to the right one of 5,743 tools across 1500 verified sources and returns a structured answer with stable pipeworx:// citation URIs. The concrete examples ('current US unemployment rate', 'Apple's latest 10-K', 'adverse events for ozempic') pin down the scope precisely. Positioning the tool as 'START HERE for most questions' makes it nearly impossible to confuse with the research, comparison, or validation siblings.

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 unusually explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', 'Use whenever the user asks...', plus a list of trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and even says to use it when web search could also answer. However, it never states when NOT to use it or redirects to sibling alternatives such as deep_research, validate_claim, or the ask_pipeworx_beta/ask_pipeworx_grounded variants, leaving that routing to inference.

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