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

The annotations already signal read-only, idempotent, open-world behavior, and the description adds substantial beyond them: account/pricing requirements, parallel routing across 5,798 tools, findings packet structure, gaps[] and contradictions[], citation_uri fetchability, semantic excerpting, and latency expectations. There is no contradiction with the 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 front-loaded with the most decision-critical facts: account requirement, when to prefer ask_pipeworx, and the core research scope. Each section adds distinct operational knowledge, though a few phrases are dense and somewhat repetitive.

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?

With no output schema, the description fully covers the return contract: verbatim evidence, confidence, source, fetched_at, citation_uri, gaps[], contradictions[], and hop field. It also covers auth, pricing, latency, and alternatives, so an agent has enough context to decide whether and how to call the tool.

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?

The schema already covers both parameters at 100%, so the baseline is 3. The description adds useful extra meaning about depth behavior (standard/thorough contradiction scans, thorough requiring a paid plan, multi-step resolution) and question suitability examples, going beyond the schema 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 states a specific verb ('research') and a specific resource ('Pipeworx's 1517 structured data sources'), and explicitly says 'this is NOT open-web search.' It also names the sibling tool ask_pipeworx as the alternative, so an agent can distinguish deep_research without opening the schema.

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 gives explicit when-to-use guidance: 'Best for broad/multi-part questions over structured data' and 'For a single lookup use ask_pipeworx instead.' It also names the exact alternative tool and the condition for choosing it: 'If you are not signed in, use ask_pipeworx instead.'

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