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

Annotations already declare read-only, open-world, non-idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely new context: the fixed USD 0.003 per-call cost, x402/USDC-on-Base payment, and that failed calls aren't charged—material facts for an agent that might otherwise retry blindly.

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?

Two tight sentences: the first front-loads what the tool returns, the second front-loads the cost/payment model. No wasted clauses and nothing buried.

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 no-output-schema tool, the description adequately describes the return shape (totals, per-coin longs/shorts, biggest ones) and time window. It could mention how the token filter interacts with the per-coin breakdown, but overall an agent has enough 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 both parameters (limit and token) are already documented in the input schema. The description adds no syntax or usage nuance beyond that, so the baseline 3 applies—the schema is doing the heavy lifting.

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 (Binance futures liquidations) with explicit scope: last hour, 190+ coins, and the breakdown returned (totals, per-coin longs/shorts, biggest ones). This clearly distinguishes it from siblings like derivatives or whale_orders without needing to name them.

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?

The data scope implies when the tool is appropriate (recent liquidation activity on Binance futures), and the pricing note hints at cost sensitivity. However, it never states when to prefer this over siblings like derivatives or whale_orders, nor any exclusions, so the agent must infer usage.

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