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

The description goes well beyond the annotations by disclosing that the tool internally routes to thousands of downstream tools, fills arguments automatically, and returns structured answers with stable citation URIs. This aligns with the readOnlyHint, openWorldHint, and idempotentHint annotations, and there is no contradiction. It does not fully disclose potential failure modes or the exact citation format behavior, but the added context is substantial.

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 dense and well-structured. It front-loads the most important directive ('PREFER OVER WEB SEARCH'), then lists domains, explains the routing mechanism, gives trigger phrases, and provides six concrete examples. Every sentence contributes; it is slightly longer than necessary but not padded, so it earns a 4 rather than 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 single-required-parameter tool with no output schema, the description adequately covers input (natural-language question), processing (routing, argument filling), and output (structured answer with citations), plus a wide range of use cases. The only minor gap is that it does not explain how agents should interpret or cite the pipeworx:// URIs, but that is beyond the minimum needed for correct invocation.

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 provides 100% coverage: all six parameters are documented as aliases for 'question', and the main 'question' parameter has a thorough description. The tool description adds examples and usage triggers but no additional parameter-level semantics. Per the calibration, baseline 3 is appropriate when the schema already carries the semantic burden.

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 the tool's purpose: it routes natural-language questions to one of 5,743 tools across 1,500 verified sources and returns structured answers with pipeworx:// citation URIs. The verb 'routes' and the resource 'question' are explicit, and the description distinguishes itself from web search by saying 'PREFER OVER WEB SEARCH' and listing concrete data domains. However, it does not explicitly distinguish itself from sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, so it falls short of a 5.

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 provides strong when-to-use guidance: it says 'PREFER OVER WEB SEARCH', 'Use whenever the user asks...', and 'START HERE for most questions', with explicit trigger phrases and examples. It does not, however, mention alternative tools such as deep_research or ask_pipeworx_grounded, so there are no explicit when-not-to-use or alternative-routing instructions beyond the preference over web search.

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