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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, but the description adds substantial behavior beyond them: account/paywall requirements, the guarantee that gaps[] are 'never invented', the parallel decomposition into 5,767 tools, latency expectations (15-60s, ~90s for thorough), citation_uri being present only when actually fetchable, and semantic excerpting rather than head-truncation. 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?

Dense but every sentence earns its place — no filler. It's front-loaded with the account requirement. Penalized slightly for being a single wall-of-text paragraph with no bullets or paragraph breaks, and for a mild redundancy where the citation_uri/fetchable guarantee is stated twice. Otherwise efficiently packed.

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?

No output schema exists, so the description correctly carries the burden of explaining return values: findings packet with verbatim evidence, confidence, source, fetched_at, gaps[], contradictions[], hop field, and citation_uri semantics. It also covers prerequisites, timing, limitations, and alternatives. Nothing an agent needs to invoke this complex tool 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; baseline is 3. The description adds real value on top: that depth:'thorough' requires a paid plan, clarifies the gap-recovery/contradictions behavior per depth level, and explains that the question param can be broad/multi-part because 'decomposition is the point'. This exceeds the baseline but doesn't add syntax-level detail the schema lacks.

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+resource: 'Grounded multi-source research across Pipeworx's 1506 STRUCTURED data sources' in one call. It sharply distinguishes from siblings by explicitly saying 'this is NOT open-web search' and naming ask_pipeworx as the alternative for single lookups, 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?

Gives explicit when/when-not guidance with named alternatives: 'If you are not signed in, use ask_pipeworx instead', 'For a single lookup use ask_pipeworx', and 'For BREAKING or colloquial CURRENT-NEWS... prefer ask_pipeworx'. Also states what it is best for ('broad/multi-part questions over structured data') with concrete example queries.

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