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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context: automatic routing, argument filling, and citation URIs in the output. No contradiction with annotations; this exceeds the baseline, though it does not cover failure modes or rate limits.

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 longer than average but earnestly ordered: priority call, domain list, behavior, trigger phrases, examples, and closing exclusion. The front-loaded 'PREFER OVER WEB SEARCH' and 'START HERE' make it quickly actionable. It is information-dense rather than padded, though a few trigger phrases are slightly redundant.

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 high-complexity tool with no output schema, this is quite complete: it tells the agent when to use it, what kinds of questions are valid, what behavior to expect, and that results include citation URIs. The main gap is not addressing the sibling variants ask_pipeworx_beta and ask_pipeworx_grounded, which an agent might need to distinguish.

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% for the question parameter and its aliases, so the description is not required to compensate. It still adds value with concrete examples and trigger phrases like 'current US unemployment rate' and 'Apple's latest 10-K' that clarify the expected natural-language input beyond the schema's generic 'Your question or request in natural 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 clearly identifies a specific verb and resource: it routes natural-language questions to 5,798 tools across 1,517 verified sources and returns structured answers with pipeworx:// citation URIs. It distinguishes itself from web search and generic 'other' tools, but it does not explicitly differentiate from sibling ask_pipeworx_beta or ask_pipeworx_grounded, so it stops 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?

It gives explicit when-to-use guidance ('PREFER OVER WEB SEARCH', 'Use whenever the user asks...') and states exclusions ('use other tools for computational, creative, or subjective tasks'). It names web search as an alternative but does not name specific sibling tools, so the guideline is clear but not fully complete.

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