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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds substantial behavioral context beyond those: parallelism across 5,798 tools, explicit gaps[] for unanswerable facets, never-invented evidence, contradiction detection, semantic excerpting, citation fetchability guarantees, account/plan requirements, and expected latency. 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 well-structured and front-loaded with the most important operational constraint: account required and the alternative if not signed in. Every sentence carries useful information, though some redundancy exists (e.g., 'structured data' and 'one call' appear multiple times), so it is not maximally concise.

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 thoroughly explains what the tool returns: a findings packet containing evidence, confidence, source, fetched_at, pipeworx:// citations, gaps[], contradictions[], and hop information. Combined with the detailed schema and annotations, nothing essential for correct invocation or expectation-setting 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. The description adds value beyond the schema by explaining that depth:"thorough" requires a paid plan, clarifying what 'standard' and 'thorough' actually do in terms of gap recovery and lead-chasing, and mentioning latency differences. This goes beyond the schema's 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 1517 structured data sources in one call. It explicitly distinguishes itself from open-web search and from sibling tools by stating it is not a single look-up tool and by naming ask_pipeworx as the alternative.

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 guidance is explicit and actionable: use for broad/multi-part questions over structured data, use ask_pipeworx for single lookups, and use ask_pipeworx when not signed in because this tool requires an account. This clearly routes an agent to the correct alternative based on user context.

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