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

Far beyond the readOnly/idempotent/openWorld annotations: discloses the auth requirement and paid gating for depth:'thorough', latency expectations (15–60s, up to ~90s), that gaps[] are explicit and never invented, that contradictions[] appear on standard/thorough, that large records are semantically excerpted rather than head-truncated, and that citation_uri is only emitted when resources/read can serve it. 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 access prerequisite is correctly front-loaded and the density is high with no filler clauses. It is a long single block with minor redundancy (citation fetchability stated twice, ask_pipeworx news routing mentioned in two places), which keeps it below a 5.

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?

There is no output schema, and the description fully compensates: it enumerates the returned fields (verbatim evidence, confidence, source, fetched_at, citation, hop, gaps[], contradictions[]), explains excerpting behavior, and sets latency expectations. Nothing an agent needs to call or interpret the result 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 baseline is 3; the description earns above baseline by explaining the behavioral consequence of each depth value (gap re-angling at standard, lead-chasing iteration at thorough) and noting that multi-step questions resolve in one call, which the schema text does not convey. The alias relationship is left entirely to the schema, which is fine.

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+scope: grounded multi-source research across 1,862 structured sources, decomposed into facets, routed to 7,167 tools in parallel, returning a findings packet. It explicitly negates what it is not ('NOT open-web search') and names the sibling it differs from (ask_pipeworx).

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?

Gives explicit selection rules with alternatives: use ask_pipeworx for a single lookup or breaking/colloquial current-news topics, use this for broad/multi-part structured-data questions (with concrete example phrasings). It also states the account/plan prerequisite and routes signed-out users to ask_pipeworx.

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