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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable behavioral context: it routes across 6,332 tools, fills arguments, returns pipeworx:// citation URIs, and is a single fast call available on every tier. It stops short of covering failure modes or limitations, so not a perfect 5.

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 every section earns its place: strong front-loaded directive, scope, alternatives, examples, and a clear 'start here' positioning. It is slightly repetitive ('PREFER OVER WEB SEARCH' and 'START HERE' say similar things), but the overall structure is effective.

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 broad routing tool with no output schema, the description is remarkably complete: it covers when to use it, what it returns, which domains it handles, example queries, alternative tools for more specialized needs, and expected performance. An agent has everything needed to decide and invoke it correctly.

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%, and the question parameter is already well described as accepting natural language with multiple aliases. The description adds no parameter-level syntax or formatting details beyond examples, so the schema carries the burden and the baseline of 3 is appropriate.

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 role: a default factual-question router that finds answers across many verified sources and returns structured answers with citations. It also distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by positioning this one as the fast default entry point.

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?

Usage guidance is explicit and well differentiated: it says to prefer this over web search, provides triggering phrases and examples, names when NOT to use it ('step up only when needed'), and names the specific sibling alternatives for those cases. This gives an agent clear selection criteria.

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