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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructiveHint. The description adds substantial context beyond those: account and paid-plan requirements, latency expectations, gaps[] never-invented behavior, semantic excerpting, and the guarantee that citation_uri is always fetchable. 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?

The description is long but information-dense, and the complexity of the tool justifies the length. It is front-loaded with the account requirement and key alternative, and then proceeds through behavior, use cases, return details, and timing. Minor redundancy with the schema's depth ladder exists, but every paragraph serves a distinct purpose.

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 must fully explain return behavior, and it does: findings packet fields, gaps[], contradictions[], hop and citation_uri semantics, and latency. Combined with the schema covering both parameters, an agent has everything needed to decide when and how to invoke this tool 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% and the schema documents both question and depth enums in detail, so the baseline is 3. The description adds value by providing example question types, clarifying that depth:'thorough' requires a paid plan, and specifying which depths return contradictions[]—context that helps an agent choose a parameter value wisely.

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 1,517 structured data sources in one call, with decomposition and parallel routing. It explicitly says this is NOT open-web search and contrasts itself with ask_pipeworx, so an agent can distinguish it from siblings without inspecting other 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?

The description gives explicit when-to-use guidance: broad/multi-part questions over structured data, with concrete examples. It also names two when-not-to-use alternatives: use ask_pipeworx for single lookups, and use ask_pipeworx when not signed in because deep_research requires an account.

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