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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, and the description adds substantial context beyond those: account/paywall requirements, not-open-web-search behavior, parallel facet decomposition, citation and gap semantics, contradictions[], semantic excerpting, and expected latency. This gives the agent a clear model of how the tool behaves and what it returns.

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 long but dense, and the most decision-critical information (auth requirement, sibling routing, open-web distinction) is front-loaded. There is minor redundancy, such as emphasizing 'one call' multiple times and a somewhat convoluted citation_uri sentence, but nearly every clause adds operational value for such a complex tool.

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 takes responsibility for explaining return contents: findings packet, verbatim evidence, confidence, source, fetched_at, stable citations, gaps[], contradictions[], and hop field. It also covers auth, pricing, latency, depth behavior, and exclusions. For a tool of this complexity, nothing essential 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 description coverage is 100%, so the schema already fully documents both question and depth. The description reinforces that broad/multi-part questions are appropriate and notes that 'thorough' requires a paid plan, but it does not add materially new semantic detail beyond the schema's already explicit enum descriptions.

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 verb and resource: grounded multi-source research across Pipeworx's 1,517 structured data sources in one call, and explicitly contrasts with open-web search. It also differentiates from ask_pipeworx by noting that a single lookup should use ask_pipeworx instead. This lets an agent reliably distinguish the tool from its many research 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?

The description gives concrete when-to-use guidance: broad/multi-part questions over structured data, with explicit alternatives for when to use ask_pipeworx (single lookup, not signed in, breaking news). It also describes depth-level behavior and latency expectations, so the agent can make informed routing decisions.

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