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

Annotations already indicate read-only, open-world, idempotent, non-destructive behavior; the description adds substantial context beyond them: required account and paid tier for thorough depth, expected latency, gaps[] never invented, contradictions[] scanning, citation_uri fetchability, and semantic excerpting behavior. This is far more than annotations alone provide.

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 front-loaded with the most critical gate ('ACCOUNT REQUIRED') and immediately names the sibling alternative. It is long but mostly purposeful for a complex tool; however, citation and resolvability details are mentioned twice, which is minor redundancy.

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 carries the full burden of explaining the return value, and it does so: findings packet with verbatim evidence, confidence, source, fetched_at, citation_uri, hop field, gaps[], contradictions[], plus latency and auth/tier requirements. Nothing essential for correct invocation appears missing.

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%, and both question and depth are already thoroughly described in the input schema. The description adds illustrative question examples and timing/account consequences, but it largely restates depth semantics already present in the schema rather than adding new parameter-level meaning.

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?

Description names a specific verb and resource: it 'decomposes your question into focused facets, routes each to ... 5,724 tools IN PARALLEL, and returns a findings packet' over Pipeworx's structured data sources. It also explicitly differentiates from open-web search and from ask_pipeworx, so an agent can select it confidently.

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 guidance: 'Best for broad/multi-part questions over structured data', plus clear alternatives and exclusions — 'For a single lookup use ask_pipeworx' and for breaking/current-news topics prefer ask_pipeworx because deep_research returns mostly empty gaps[]. It also notes the account/tier prerequisite.

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