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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses many behavioral traits: account requirement, paid tier for 'thorough', 15-90s latency, gap[] reporting, contradictions[] scans, guaranteed-fetchable citation_uri, and semantic excerpting rather than head-truncation. It also states that findings are 'never invented'. No contradiction with annotations was found.

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?

Though long, the description is densely packed with high-value information and each sentence earns its place: auth requirements, sibling routing, scope, output guarantees, depth behavior, citation semantics, and latency. The most decision-critical information (account required, alternative tool) is front-loaded, and the rest is organized logically. This length is appropriate given the tool's complexity and the absence of an output schema.

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, the description is remarkably complete: it explains the findings packet, gaps[], contradictions[], citation_uri fetchability, hop field, deep-record excerpting, latency, and tier differences. Combined with a fully covered input schema and accurate annotations, an agent has nearly everything needed to decide whether to call this tool and what to expect. The only minor absence is a concrete JSON shape, but the description describes the return contract well enough.

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, and the schema already documents both question and depth including the quick/standard/thorough semantics. The description adds meaningful value by tying 'thorough' to a paid plan, explaining hop/gap-recovery behavior, describing latency expectations, and giving concrete example questions. It does not need to add syntax details because the schema already provides those.

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-resource pair: it performs grounded, multi-source research across Pipeworx's structured data sources. It clearly distinguishes itself from open-web search and from ask_pipeworx by positioning itself for broad/multi-part questions while directing single lookups to the sibling. The mechanism (facet decomposition, parallel routing, findings packet) makes the tool's function 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 it for broad/multi-part questions over structured data, and use ask_pipeworx instead for single lookups. It also handles the non-signed-in case by redirecting to ask_pipeworx, and clarifies tier-based depth availability. This is strong alternative-routing with concrete conditions.

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