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

The annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds substantial behavioral context beyond that: internal routing across thousands of tools, automatic argument filling, stable pipeworx:// citation URIs in the response, one-fast-call performance, and availability on every tier. It also signals that hallucination-resistant verbatim evidence requires the grounded sibling, implying the base tool's limits without contradicting 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 long but information-dense and front-loaded with the most important guidance ('PREFER OVER WEB SEARCH'). Every section earns its place: scope, examples, default positioning, and escalation conditions. It could be tightened slightly, but for a broad meta-tool the length is purposeful rather than verbose.

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?

Given the tool's broad scope and lack of an output schema, the description is remarkably complete. It explains what the tool does, when to use it, when not to use it, what output format to expect (structured answer with citation URIs), and how it behaves on edge cases like breaking news. The aliases and examples in the schema cover the input side, so nothing essential is missing 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?

Schema description coverage is 100%, with every parameter documented as an alias for 'question'. The description adds nothing about parameter formats, but the schema already documents all six aliases and includes three realistic examples. This meets the baseline of 3: the structured schema does the heavy lifting and the description does not need to compensate.

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 states a specific role: it routes factual questions to one of 5,724 tools across verified sources and returns structured answers with citation URIs. It clearly distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives with different strengths. It also provides concrete examples of the question types it handles.

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 explicitly instructs the agent to prefer this tool over web search for factual questions and positions it as the default entry point. It names the exact conditions under which to step up to ask_pipeworx_grounded or deep_research, and even clarifies that ask_pipeworx handles breaking-news queries via live news feeds. This leaves no ambiguity about when to select this tool.

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