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

Annotations already cover read-only, open-world, idempotent, non-destructive behavior. The description adds useful behavioral context: it routes/fills arguments and returns a structured answer with stable pipeworx:// citation URIs. No contradiction with annotations, but no extra detail on latency or failure behavior.

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 most important directive and is information-dense, but it is somewhat repetitious ('even if web search could also answer it' and 'START HERE for most questions' restate earlier guidance). It ends with a stray ellipsis that suggests truncated content, which hurts 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?

For a single-parameter tool with rich annotations, the description covers the core information an agent needs: when to use it, what data domains it supports, example questions, and the citation-bearing response shape. The lack of explicit guidance about sibling variants and edge cases is a minor gap.

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 parameter is self-explanatory, so the baseline is 3. The description adds value with a breadth of example questions and trigger language ('what is', 'look up', 'current'), helping an agent formulate the single required question parameter.

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 the tool as a factual question router: 'Routes the question to the right one of 5,798 tools across 1517 verified sources' and says it returns structured answers with citation URIs. It is specific about domains and trigger phrases, but it does not explicitly distinguish ask_pipeworx from sibling variants like ask_pipeworx_beta and ask_pipeworx_grounded.

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?

Extremely explicit about when to prefer it: 'PREFER OVER WEB SEARCH' for factual/current/historical data, with trigger phrases and concrete examples, and 'START HERE for most questions.' It offers no explicit when-not-to-use guidance or alternatives beyond web search, so it stops short of a 5.

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