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

Annotations already mark the tool read-only, open-world, idempotent, and non-destructive, and the description adds substantial behavioral context beyond that: account/payment requirements, parallel decomposition, explicit gaps instead of invented answers, contradiction reporting, citation fetchability guarantees, 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 densely informative, covering purpose, scope, alternatives, output shape, parameter effects, and latency. It front-loads the critical account requirement and alternative routing. Some redundancy exists in repeated ask_pipeworx guidance, but every section earns its place given the tool's complexity.

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 covers the full invocation picture: prerequisites, parameter semantics, output packet structure, gap/contradiction behavior, citation resolvability, use-case boundaries, and expected latency. An agent has enough context to select and call the tool correctly.

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. The description adds meaningful semantic context beyond the schema by noting 'thorough' requires a paid plan and clarifying how depth levels affect hop behavior, gap recovery, and contradiction scanning in relation to the question parameter.

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 and resource: grounded multi-source research over 1540 structured data sources, decomposed into facets and routed in parallel. It clearly distinguishes itself from open-web search and names the sibling ask_pipeworx as the alternative for other use cases.

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 structured-data questions, and explicit when-not-to-use guidance: single lookups, current events, open-web topics, or unsigned-in users, all pointing to ask_pipeworx. This leaves no ambiguity about tool selection.

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