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

Annotations already mark this as read-only, open-world, idempotent, and non-destructive, and the description goes far beyond that. It discloses the parallel decomposition behavior, the findings packet structure, explicit gaps[] for unanswered facets, contradiction[] scanning for standard/thorough, stable fetchable pipeworx:// citations, semantic excerpting rather than head-truncation, and expected latency ranges. No annotation contradiction exists.

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 and dense, but nearly every sentence adds necessary operational or behavioral detail for a complex tool. It is not perfectly front-loaded, opening with account requirements rather than the core action, and the long parenthetical chains reduce skimmability, but the density is largely justified.

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?

For a tool with no output schema and only two parameters, this description carries a heavy burden and succeeds. It covers authentication, pricing tiers, routing behavior, output format, citation semantics, limitation handling via gaps[], contradiction detection, record excerpting, and latency expectations — nothing an agent needs to call it correctly is 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 significantly enriches parameter understanding. It explains exactly what each depth value means — quick=3 single hop, standard=3 with gap recovery plus contradictions, thorough=6 with iterative lead-chasing and gap recovery — and clarifies that the question parameter accepts broad natural language because decomposition is the point.

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 clearly states a specific action: grounded multi-source research over 1,517 structured data sources in one call, decomposing questions and routing facets to thousands of tools in parallel. It explicitly distinguishes itself from open-web search and from ask_pipeworx, which makes its role among siblings 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: best for broad/multi-part questions over structured data, and single lookups should use ask_pipeworx instead. It also states the account requirement, the paid tier requirement for 'thorough', and tells unsigned-in users to use ask_pipeworx, 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.