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

Even though annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, the description adds substantial behavioral context: account requirements, parallel decomposition into 5,908 tools, findings packet structure with gaps[], contradiction scanning, citation URI fetchability, semantic excerpting, and expected latency. Nothing contradicts the 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 highly informative but overlong and somewhat disorganized. It mixes account requirements, usage guidelines, depth mechanics, and return details in a dense paragraph, plus a malformed `depth:"thorough"` string. Every point is valuable, but the structure would benefit from clearer separation and more scannable formatting.

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 thoroughly explains the return value shape: findings packet with verbatim evidence, confidence, source, fetched_at, citation_uri, gaps[], contradictions[], and hop field. It also covers depth-specific behavior, latency, and what happens when the topic is not in the structured catalog, leaving no critical information for the agent to infer.

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?

The input schema already fully documents both parameters, so the baseline is 3. The description earns a 4 by adding critical semantics not present in the schema: 'thorough' requires a paid plan, 'standard' and 'thorough' enable contradiction detection, and depth variants differ in hop behavior and gap recovery.

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 the tool performs grounded multi-source research over Pipeworx's 1540 structured data sources in a single call, explicitly calling out that it is NOT open-web search. It also contrasts with ask_pipeworx for single lookups, making the purpose and distinction from 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?

Provides explicit when-to-use and when-not-to-use guidance: 'Best for broad/multi-part questions over structured data', 'For a single lookup use ask_pipeworx', and 'If you are not signed in, use ask_pipeworx instead'. It also warns against confusing it with open-web search, giving an agent clear routing criteria.

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