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

Annotations are readOnly/openWorld/idempotent/non-destructive, and the description is consistent with them while adding substantial context: auth needs, tier costs, latency bounds (15-60s, thorough up to ~90s), the gaps[] never-invented policy, contradictions[] for standard/thorough, semantic excerpting of long records instead of head-truncation, and the guarantee that returned citations are resolvable pipeworx:// URIs.

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 content is genuinely high-value, but it is delivered as a dense wall of run-on sentences and parenthetical asides, with the ask_pipeworx fallback stated twice and depth semantics effectively repeated across the auth preamble, the schema, and the body. A few line breaks and one consolidated depth explainer would make it scanable much faster.

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 must explain return values itself, and it does exhaustively: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citation, gaps[], contradictions[], and the hop field. It also coers auth, pricing, latency, unanswerable-facet behavior, and citation resolvability — nothing an agent needs to invoke this correctly 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 schema already documents both parameters in detail — including depth's quick/standard/thorough hop semantics and the paid flag. The description adds only a light framing nudge ('Broad/multi-part is fine — decomposition is the point') and restates depth behavior already present in the schema, so it does not meaningfully go beyond the baseline.

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: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources ... in ONE call' with a hard line against open-web search ('this is NOT open-web search'). It also differentiates itself from siblings by naming ask_pipeworx as the fallback and describing the decompose-and-route-in-parallel mechanics that no other tool shares.

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 when-to-use guidance ('Best for broad/multi-part questions over structured data' with concrete examples) and when-not-to-use guidance ('For a single lookup use ask_pipeworx instead'). It also states the access precondition up front: unsigned-in users should route to ask_pipeworx because it works on every tier, and thorough depth requires a paid plan.

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