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

Even though annotations already mark readOnly/openWorld/idempotent, the description adds substantial behavioral context: account/plan requirements, parallel decomposition into 5,743 tools, gaps[] for unanswered facets, contradictions[] for deeper depths, stable fetchable citations, semantic excerpting, and expected latency. 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 dense and front-loaded with the most important caveat (account required), but it is a long single block with nested parentheticals. Every sentence carries signal, though splitting it into clearer sections would improve structure.

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 carries the burden of explaining the return value: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citations, gaps[], contradictions[], hop fields, and citation_uri. It also covers auth, latency, and when not to use the tool, so an agent can invoke and interpret it 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% and the schema already documents both params well, so the baseline is 3. The description adds extra value by clarifying the question's broad/multi-part style, the paid requirement for thorough depth, and time expectations tied to depth choices.

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 1500 structured data sources in one call. It explicitly distinguishes itself from open-web search and differentiates itself from sibling tools like ask_pipeworx, so an agent can tell what it does and what it is not.

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: best for broad/multi-part questions over structured data, and for single lookups use ask_pipeworx instead. It also covers the signed-out fallback and explains how depth levels map to iterative question resolution.

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