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

Annotations already signal readOnly/openWorld/idempotent, and the description adds substantial behavioral context: account requirements, paid tier, gap handling ('never invented'), contradiction reporting, resolvable citation_uri, semantic excerpting, and latency expectations. No contradiction with 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 but dense and well-organized: caveats and alternatives are front-loaded, followed by mechanics, output shape, and latency. Every sentence earns its place; there is no filler or repetition of schema boilerplate.

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 must explain the return shape, and it does: findings packet, evidence, confidence, source, fetched_at, gaps[], contradictions[], hop, and citation_uri. It also covers prerequisites, depth behavior, timing, and sibling routing, making it complete for 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?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds value by explaining what the depth levels actually do (hop/gap-recovery/contradictions) and by clarifying that the question can be broad/multi-part, though some of this reinforces the schema rather than adding new syntax.

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 action and resource: grounded multi-source research over Pipeworx's structured data sources. It clearly distinguishes itself from open-web search and from sibling ask_pipeworx, with concrete examples that signal the intended question type.

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 explicitly says when to use this tool ('best for broad/multi-part questions over structured data') and when not to ('for a single lookup use ask_pipeworx instead'). It also handles the signed-out fallback, routing agents to ask_pipeworx if no account is available.

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