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

Annotations already mark it readOnly, open-world, idempotent, and non-destructive, and the description adds substantial context: account and paid-tier requirements, parallel routing to thousands of tools, transparent gap reporting with no invented answers, contradictions scan, citation resolvability, semantic excerpting, and expected latency. There is no contradiction with 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 long and dense, but the complexity of the tool justifies most of the detail. It is front-loaded with the account constraint and alternative routing, followed by the core purpose and then behavioral nuances. It is somewhat rambling and could be tightened, but no sentence is filler.

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?

There is no output schema, so the description correctly carries the full burden of explaining return values: findings packet contents, gaps, contradictions, hop field, citation URIs, and fetchability. It also covers auth, tier behavior, latency, and alternative tools, so an agent has everything needed to call 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%, so the baseline is 3, and the description goes beyond the schema by explaining what each depth level actually does: quick is single-hop, standard adds gap recovery and contradictions, thorough adds an iterative chase and requires payment. It also provides example questions that clarify what the question parameter is for.

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 names a specific verb and resource: grounded multi-source research over Pipeworx structured data sources in one call, with decomposition and parallel routing. It explicitly distinguishes itself from open-web search and from ask_pipeworx for single lookups. This gives an agent a clear basis for selecting it over the many sibling tools.

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 concrete when-to-use guidance: best for broad or multi-part questions over structured data, with examples. It also states when-not-to-use: if not signed in, use ask_pipeworx instead, and for a single lookup use ask_pipeworx. This is explicit alternative routing.

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