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

Even though annotations already declare readOnlyHint/openWorldHint/idempotentHint, the description adds substantial behavioral context: account and paid-tier requirements, 15-90s latency windows, the never-invented gaps[] guarantee, contradictions[] on standard/thorough, conditional citation_uri presence, semantic excerpting instead of head-truncation, and multi-hop resolution. Nothing in the description contradicts the 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 dense and front-loaded with the most operationally critical facts (account requirement, fallback tool), and every sentence carries useful information. However, it runs long (~280 words), contains a garbled segment ('For BREAKing or colloquial topics... *-news-feeds packs') that could confuse parsing, and partially restates depth behavior already documented in the schema enum.

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 present, the description carries the full burden of explaining return values, and it does so thoroughly: findings packet fields (verbatim evidence, confidence, source, fetched_at), stable pipeworx:// citations, gaps[], contradictions[], hop field, and the conditionality of citation_uri. For a tool this complex, nothing essential an agent needs to call it 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 baseline is 3, but the description adds value beyond the schema: it ties the depth enum to latency expectations (15-60s, thorough up to ~90s), explains what gap-recovery and lead-chasing mean operationally, and reinforces that broad/multi-part questions are appropriate for the question parameter. It enriches parameter understanding without having to carry the burden.

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 1496 STRUCTURED data sources... in ONE call.' It differentiates itself from siblings explicitly by noting 'this is NOT open-web search' and contrasting with ask_pipeworx for single lookups. An agent can clearly tell this tool from its siblings without inspecting 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?

Usage conditions are explicit and exhaustively branched: 'If you are not signed in, use ask_pipeworx instead'; 'Best for broad/multi-part questions over structured data' with concrete example queries; 'For a single lookup use ask_pipeworx'; and for breaking/colloquial topics 'prefer ask_pipeworx.' Every alternative is named directly, so no inference is required.

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