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

The annotations already mark the tool read-only, open-world, idempotent, and non-destructive. The description goes far beyond that by disclosing internals: question decomposition, parallel routing, the findings packet structure, gap reporting, contradiction detection, no invented evidence at the gaps, the conditional citation_uri behavior, semantic excerpting, and expected latency. This is unusually rich behavioral disclosure with no contradiction.

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 dense and front-loaded with the most decision-critical facts: account requirement, free tier, and the sibling to use when unsigned. It is long but packed with useful behavioral detail; some awkward parenthetical asides and overlapping depth explanations make it slightly heavier than ideal, 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?

For a complex research tool with no output schema, the description explains what the agent should expect back: evidence, confidence, source, fetched_at, citations, gaps[], contradictions[], and fetchable citation URIs. Combined with the high-coverage schema and annotations, nothing critical is missing 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?

Input schema coverage is 100%, so baseline is 3. The description does not add meaningfully to the parameters beyond what the schema already explains; depth behavior and the question's broad/multi-part nature are both already captured in the schema descriptions. It provides context for timing but not independent parameter semantics.

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 action — grounded multi-source research over Pipeworx's 1,517 structured data sources in a single call — and clearly marks it as distinct from open-web search. It also differentiates from siblings like ask_pipeworx by specifying its best use for broad/multi-part questions.

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 explicit when-not-to-use guidance: if not signed in use ask_pipeworx, and for a single lookup use ask_pipeworx instead. It also notes tier restrictions for depth options, leaving little room for mis-selection.

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