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

Annotations already mark readOnly, openWorld, idempotent, and non-destructive; the description adds substantial context: account requirements, paid tier for thorough, findings packet with verbatim evidence, gaps[] honesty, contradictions[], citation fetchability, 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?

The description is an extremely long single paragraph with a large repetitive tail: 'For a single lookup use ask_pipeworx.' is repeated dozens of times. Important info is front-loaded, but the redundancy and wall-of-text structure waste agent attention and violate the 'every sentence earns its place' principle.

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?

Even without an output schema, the description fully explains return shape (findings packet, citations, gaps[], contradictions[]), prerequisites, depth mode differences, timing, and the structured-data grounding. Nothing an agent needs to call it correctly 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?

Both parameters are fully documented in the schema (100% coverage), including depth semantics. The description adds latency expectations and clarifies that broad/multi-part questions are fine, but it does not meaningfully extend beyond the schema's parameter descriptions. Baseline 3 applies.

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?

States the verb 'research' across 1517 structured data sources in one call and explicitly says it is NOT open-web search. It contrasts with ask_pipeworx for single lookups, so an agent can distinguish it from siblings. The resource and scope are concrete and specific.

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?

Gives explicit when-to-use guidance: broad/multi-part questions over structured data, with concrete examples. Also gives when-not-to-use: single lookups should use ask_pipeworx, and unsigned users should use ask_pipeworx because it works on every tier. This directly routes the agent to the correct alternative.

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