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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, and the description still adds substantial context beyond them: a 100 calls/day free limit, 0.002 USDC per call afterward, prepaid batches of ~0.01 USDC, and a payment-required response carrying an exact amount plus payment_token. It also warns data may be delayed or wrong and is not financial advice.

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 core behavior is front-loaded in the first sentence, followed by scoping and payment terms. It is dense but every sentence carries operational information; the payment sentence is long but necessary given the prepaid model.

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?

There is no output schema, so the description carries the return-value burden, and it does: it enumerates the metrics per pool and the top-pools list. Combined with the payment flow explanation, an agent has everything needed to call it 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 the mutual-exclusivity relationship (top only when no pool is given, custom window_hours only for a single pool) and frames payment_tx/payment_token as a post-free-tier workflow tied to the payment-required response, which is more than the schema's field-level 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?

Names the exact resource and metrics returned — '24h volume, high/low, last price and % change' — and the alternate branch ('top pools by 24h quote volume if no pool is given'). This is far more specific than siblings like get_pool_stats or get_ohlcv, so an agent can route to it without opening the schema.

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?

Gives clear branch conditions: pool omitted returns top pools, and window_hours applies only to a single pool. It also explains the payment path when the free tier is exhausted. It stops short of naming an alternative sibling (e.g., get_pool_stats) for when a different metric view is wanted.

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