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

Annotations already declare read-only/idempotent; description adds account requirement, paid plan for thorough, exact return packet (evidence, confidence, source, citation, gaps[]), a guarantee it never invents answers, the one-call/no-agents/no-files constraint, and timing. Also states standard/thorough include contradiction scans.

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?

Long but efficient — the account/tier warning, alternative, scope, return format, and timing all earn their place. Slight redundancy between 'not open-web' and 'not autonomous deep research' but both clarify potential confusion.

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 tool with no output schema, the description covers everything an agent needs: prerequisites, alternatives, behavior, return fields, latency, and parameter guidance. No practical gaps.

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 already covers both parameters (100%); description adds the paid-plan constraint on depth and clarifies that question should be broad/multi-part, which is useful context beyond the enum text.

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?

States a specific verb (research), a resource (1,540 structured data sources), and a mode (one call, parallel routing to 5,908 tools). Explicitly distinguishes from ask_pipeworx (single lookup) and open-web search, and clarifies the name is not an autonomous multi-agent loop.

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?

Explicitly says 'Best for broad/multi-part questions over structured data' and 'For a single lookup use ask_pipeworx instead.' Also routes unsigned users to ask_pipeworx with a tier note. No ambiguity about when to pick this tool.

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