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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already establish a safe read operation, and the description adds substantial context beyond that: parallel decomposition into facets, routing across 5,798 tools, gaps[] for unanswered facets, never-invented behavior, hop and citation_uri semantics, contradictions[] scans for standard/thorough, semantic excerpting, and latency expectations. This far exceeds the annotation baseline.

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?

This is a dense but poorly organized wall of text. The account requirement is front-loaded ahead of the actual purpose, depth semantics are scattered across the description rather than consolidated, and there are typographic/formatting artifacts (e.g., 'depth:"thorough"', odd quote/contraction patterns). Much of the content earns its place, but its structure undermines readability.

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, so the description correctly carries the burden of explaining the return value: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citation per finding, gaps[], and contradictions[]. Combined with the depth semantics, auth requirements, and latency ranges, everything an agent needs to correctly invoke and interpret this tool is present.

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% (both question and depth are documented in the schema), so the baseline is 3. The description adds meaning beyond the schema: it explains the behavioral difference between depth levels (quick=3 single hop, standard=3 with gap recovery + contradictions, thorough=6 paid with a lead-chasing iterative hop) and ties latency expectations to depth. This is genuine added value.

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 verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources... in ONE call'. It explicitly distinguishes itself from open-web search and names ask_pipeworx as the alternative for single lookups, so an agent can tell it apart from siblings without opening the schema.

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?

Explicit when/when-not guidance is present: 'If you are not signed in, use ask_pipeworx instead', 'Best for broad/multi-part questions over structured data', and 'For a single lookup use ask_pipeworx instead'. The account and paid-plan prerequisites are also stated up front, leaving no ambiguity about who may call it.

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