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

Annotations already carry the safety profile (readOnly=true, openWorld=true, idempotent=true, destructive=false), so the bar is lower. The description adds genuine context beyond annotations: stable citation URIs in the return, 'works on every tier, one fast call' latency/availability, and the routing behavior to live news. No contradiction with 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 (~180 words) but front-loaded with the key directive and every sentence earns its place: domains, trigger phrases, examples, sibling routing, and tier notes are all decision-relevant. Slightly longer than ideal, but the routing complexity justifies the density.

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?

With no output schema, the description correctly explains the return value (structured answer with pipeworx:// citation URIs). It covers selection criteria, invocation phrasing, alternatives, and behavior. Minor gaps only: no error/edge behavior or input limits, but for a single-natural-language-parameter tool this is nearly complete.

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% — the sole meaningful parameter 'question' is fully documented along with its five aliases. The description adds marginal value through example questions ('current US unemployment rate', 'Apple's latest 10-K') that illustrate formatting, but the schema already does the heavy lifting, so baseline 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?

States a specific verb+resource: 'Routes the question to the right one of 5,743 tools... returns the structured answer with stable pipeworx:// citation URIs.' It explicitly differentiates from siblings by naming ask_pipeworx_grounded (hallucination-resistant single answer) and deep_research (broad fan-out), so an agent can tell them apart without opening schemas.

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?

Exceptionally explicit: opens with 'PREFER OVER WEB SEARCH,' lists covered domains, gives trigger phrases ('what is', 'look up', 'find', 'get the latest'), provides concrete examples, declares 'START HERE for most questions — this is the default entry point,' and names precise step-up conditions for ask_pipeworx_grounded and deep_research. Nothing is left to inference.

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