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

Even though annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, the description adds substantial behavioral context: account/tier requirements, parallel decomposition across 5,718 tools, 15-90s latency, gaps[] semantics, contradictions[], resolvable pipeworx:// citation_uri, and semantic excerpting. These are consistent with the annotations, so there is no contradiction.

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 dense and front-loaded with the account gate followed by capability, alternatives, and depth behavior. Nearly every sentence carries distinct operational information, though a few depth details are repeated from the schema, preventing a perfect score.

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?

There is no output schema, but the description thoroughly specifies the findings packet structure, citation behavior, gaps[] and contradictions[], auth requirements, latency envelope, and sibling routing. Nothing essential for correct invocation or result interpretation appears to be 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%, but the description goes further by adding operational meaning: depth:'thorough' is paid, quick/standard run 3 facets, standard re-angles gaps, thorough chases leads, and question explicitly accepts broad/multi-part natural language. It slightly overlaps with the schema's enum descriptions, but it still adds real value.

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 and resource: 'Grounded multi-source research across Pipeworx's 1496 STRUCTURED data sources' in ONE call. It explicitly says 'this is NOT open-web search' and distinguishes itself from ask_pipeworx, so an agent can recognize both what it does and what it does not do.

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, use ask_pipeworx for single lookups, prefer ask_pipeworx for breaking/current-news topics, and use ask_pipeworx if not signed in. This leaves no ambiguity about sibling selection.

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