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

Annotations already carry the readOnly/idempotent safety profile, so the bar is lower; the description still adds rich behavior: decomposition into facets, parallel routing to 5,798 tools, findings packets with confidence/source/citation, explicit gaps array, contradiction scans, semantic excerpting, latency ranges, and paid-depth restrictions. There is no contradiction with the readOnlyHint.

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 definition is dense and information-rich, front-loading the account gate and the ask_pipeworx alternative before the core capability. It is longer than average, but nearly every sentence contributes behavioral or routing detail; minor redundancy in mentioning ask_pipeworx twice keeps it from being a 5.

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?

Since there is no output schema, the description correctly carries the return-value burden by naming the findings packet fields: verbatim evidence, confidence, source, fetched_at, pipeworx citation, gaps, contradictions, hop, and citation_uri. It also covers input scope, latency, auth requirements, and depth semantics, leaving no major gap for correct invocation.

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 description coverage is 100% and both question and depth are well documented in the schema, so the baseline is 3. The description adds value by explaining depth-specific behavior such as gap-recovery hops, contradiction scans, the paid thorough tier, and expected latency beyond the schema's enum text.

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 precise verb-plus-resource: grounded multi-source research across Pipeworx's 1517 structured data sources, and explicitly says it is NOT open-web search. It also distinguishes itself from ask_pipeworx by positioning itself for broad/multi-part questions while directing single lookups to that sibling.

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, with concrete examples. It also warns about account requirements and tells agents to use ask_pipeworx if not signed in, preventing failed invocations.

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