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

Annotations already mark it read-only/idempotent, and the description adds far more: account gating, parallel decomposition across 5,724 tools, the findings-packet shape, gaps[] and contradictions[], second-hop recovery behavior, semantic excerpting, and latency expectations. It clearly sets expectations about when results will be empty ('never invented'). No contradiction with annotations is apparent.

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 account requirement and the critical 'NOT open-web search' caveat. Each sentence delivers useful behavior, though there is some redundancy around ask_pipeworx routing and repeated mention of gaps[]/contradictions[]. It could be tightened modestly without losing signal.

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?

Despite having no output schema, the description enumerates the full response shape (verbatim evidence, confidence, source, fetched_at, pipeworx:// citation, gaps[], contradictions[], hop field), clarifies citation resolvability, and covers timing and depth-specific behavior. For a complex research tool, this is unusually complete.

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 meaningful depth semantics beyond the schema: it explains that 'standard' re-angles unanswered gaps, 'thorough' chases leads and requires a paid plan, and that natural-language multi-part questions are expected. This goes beyond simply restating the parameter names.

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 names the specific verb-resource pair (grounded multi-source research across Pipeworx's 1497 structured data sources), scopes it explicitly with 'this is NOT open-web search,' and distinguishes it from ask_pipeworx. It gives concrete examples of the broad/multi-part questions it is designed for.

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?

Provides explicit when-to-use versus when-not-to-use guidance: use for broad/multi-part structured-data questions, use ask_pipeworx for single lookups or breaking/colloquial news, and use ask_pipeworx if not signed in. It also states account/tier prerequisites and expected latency.

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