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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds substantial context beyond those: account/paid-tier requirements, parallel routing to 5,743 tools, gaps[] for unanswered facets, contradictions[], hop fields, fetchable citation_uri guarantees, semantic excerpting, and latency expectations. It clearly explains the tool's safety and execution profile without contradicting 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 information-dense; nearly every sentence earns its place by adding operational detail (account requirements, latency, citation fetchability, excerpting behavior). It is front-loaded with the most critical caveat (account required) and the primary alternative. Some depth-level detail is somewhat redundant with the schema, but not to a distracting degree.

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 must explain return behavior, and it does: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citations, gaps[], contradictions[], hop field, and citation_uri semantics. It also covers preconditions, latency, and exclusions. An agent has enough context to decide when to call this tool and roughly what to expect back.

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, but the description adds meaning beyond the schema: it clarifies that 'question' should be natural language and that broad/multi-part questions are appropriate, and it elaborates how depth levels affect hops, gap recovery, contradiction scanning, and latency. This is genuine added value, though the schema already carries the core parameter definitions.

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-resource pair: 'Grounded multi-source research across Pipeworx's 1500 STRUCTURED data sources' in one call. It explicitly differentiates itself from open-web search and from sibling tools like ask_pipeworx, making the tool's scope unmistakable.

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: use for broad/multi-part structured-data questions, use ask_pipeworx for single lookups and for breaking/current-news topics. It also names a fallback when not signed in ('use ask_pipeworx instead'), leaving no ambiguity about tool selection.

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