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

Annotations cover read-only, idempotent, open-world, and non-destructive traits, and the description adds substantial behavior: parallel decomposition across 5,798 tools, findings packet contents, gaps[] never invented, contradiction scan, hop field, fetchable citation_uri, semantic excerpting, and latency expectations. 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?

Front-loaded with auth requirement and core purpose, but the description is long and slightly repetitive, with citation/findings details appearing multiple times. It earns most of its length through genuinely useful operational details, though tighter editing would improve it.

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?

For a complex tool with no output schema, the description is remarkably complete: it explains auth tiers, alternatives, output format, citation resolvability, gaps behavior, depth meanings, and expected latency. An agent has everything needed to select and invoke it correctly.

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; the description adds value by elaborating depth modes (quick single-hop vs standard gap recovery vs thorough paid iterative hop) and clarifying that the question parameter is meant for broad/multi-part natural language. This is useful context beyond the schema, though not required for basic invocation.

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 a specific action (grounded multi-source research) with a clear resource scope (1517 structured data sources, not open-web search) and distinguishes it from ask_pipeworx for single lookups. It also states the decomposed parallel research behavior and output, which fully separates it from siblings.

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?

It explicitly says to use ask_pipeworx when not signed in, recommends deep_research for broad/multi-part questions over structured data, and directs single lookups to ask_pipeworx. This provides both positive and negative usage guidance with a named alternative.

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