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

Annotations already mark this read-only/open-world/idempotent, and the description adds meaningful behavior: auth requirements, 15-90s latency, findings packet structure, gaps[] never invented, contradictions[], resolvable pipeworx:// citations, and semantic excerpting. Nothing in the description contradicts 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 text is dense and front-loaded with the most decision-critical info (auth, alternative tool, core definition), and most sentences add unique detail. It is somewhat long and the 'use ask_pipeworx instead' guidance appears twice, which keeps it from perfect concision.

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 compensates by specifying the findings packet fields, gap/citation/contradiction semantics, latency, and auth tiers. An agent has enough to select, invoke, and interpret results 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%, so the baseline is 3, and the description goes further by explaining what depth levels do (standard re-angles gaps, thorough chases leads and adds contradiction scan) and by giving example question shapes for the question parameter. This adds real semantics beyond the 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 action and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' in one call, and contrasts itself with open-web search. It also explains the decomposition-and-parallel-routing mechanism, making the tool's function unmistakable and distinct from 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 clear decision rules: use it for broad/multi-part questions over structured data, and explicitly says 'For a single lookup use ask_pipeworx instead' and to use ask_pipeworx if not signed in. It also states account and paid-tier prerequisites, so an agent can route correctly.

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