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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds genuinely useful behavioral context: it routes the question to one of 5,908 tools, fills arguments automatically, and returns a structured answer with stable pipeworx:// citation URIs. It does not contradict the annotations.

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 the most important directive, then moves from scope to behavior to examples to sibling routing. Every sentence earns its place; the length is justified by the breadth of factual domains and routing guidance.

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 clearly states the return format: structured answers with stable pipeworx:// citation URIs. It also covers when to prefer this tool over web search, when to use sibling tools, and what types of questions it handles. No essential decision-making information is missing.

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%, so the description does not need to document each parameter. It adds value through trigger phrases and concrete examples like 'current US unemployment rate' and 'Apple's latest 10-K', which help an agent understand the natural-language input style 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 leads with 'PREFER OVER WEB SEARCH' and a specific verb-resource pair: answering factual questions about current or historical data. It enumerates concrete domains and explains that the tool routes to 5,908 verified tools, making it clear what ask_pipeworx does and how it differs from siblings like ask_pipeworx_grounded and deep_research.

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 trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'), real examples, and a clear default: 'START HERE for most questions'. It also names alternatives with selection conditions: ask_pipeworx_grounded for hallucination-resistant single 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.