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

Adds substantially beyond the annotations: the data is read-only but metered, at $0.003 per successful call via x402 USDC-on-Base payment passed in _meta, with bad input and sub-2-feed responses free. It also discloses upstream feed coverage gaps, which the annotations (readOnly/openWorld/idempotent=false) cannot convey.

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?

Front-loaded with the core verb and resource, with the price/payment mechanics last, which is the right ordering. It is dense and somewhat run-on, and the clause 'Liquidation data for BTC, ETH, SOL and more' partly repeats the coin parameter, but no sentence is wasted.

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?

With no output schema, the description compensates by sketching the return shape (per-venue long/short USD, totals, largest events) and by covering cost, payment mechanism, billing edge cases and coverage limits. An agent has everything needed to decide and invoke 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 the coin symbol formats and the 1-24 default-24 window are fully documented in the schema. The description only restates the coin universe (BTC, ETH, SOL) and the hour range, adding no syntax or edge-case guidance beyond the structured fields, so baseline 3 applies.

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 resource (perpetual-futures liquidations for one coin), the exact measures returned (long/short liquidations in USD per venue, totals, largest events) and the time window. Names the covered venues (Gate, Bitfinex, dYdX, Deribit, OKX) and the non-covered ones, which no sibling tool does, so it is unmistakable against derivatives_snapshot or open_interest.

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 operative context: one coin at a time, 1-24h look-back, and an explicit coverage exclusion list (Bybit, Hyperliquid, Kraken are WebSocket-only and not serviced) that tells the agent when the tool will fail. It does not point to any alternative sibling for related derivatives metrics, so it falls short of a full when/when-not/alternatives statement.

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