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

The description discloses account requirements, paid-plan gating, parallel routing across 5,767 tools, the findings packet structure (verbatim evidence, confidence, source, fetched_at, pipeworx:// citation), explicit gaps[] behavior, 'never invented', a latency estimate, and the non-open-web nature. These go well beyond the read-only/idempotent annotations and add meaningful operational context.

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 yet efficiently front-loaded: account requirement, fallback, scope, mechanism, output, best-use, and exclusions each get a clear sentence. The only near-repetition (ask_pipeworx mentioned twice) is justified because it addresses two distinct conditions: not signed in vs. single lookup.

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, multi-faceted research tool with no output schema, the description fully covers prerequisites, alternatives, behavior, return format, latency, limitations, and ideal use cases. An agent has everything needed to decide when to call it and what to expect in return.

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; however the description adds useful question-parameter semantics by explaining that the question is decomposed into focused facets routed in parallel, and gives concrete examples of appropriate questions. It also reinforces that 'thorough' carries a paid requirement, which the schema already notes but the description contextualizes.

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 verb ('research') and resource ('Pipeworx's 1506 STRUCTURED data sources'), explicitly distinguishes itself from open-web search, and names the sibling alternative ask_pipeworx. The 'this is NOT open-web search' clarification prevents category confusion.

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 the tool ('Best for broad/multi-part questions over structured data'), when not to ('For a single lookup use ask_pipeworx instead'), and the auth condition ('If you are not signed in, use ask_pipeworx instead — it works on every tier'). It also clarifies the paid-tier requirement for 'thorough' depth.

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