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

It discloses the two traits annotations can't convey: the $0.005 per-call cost and the USDC-on-Solana x402 payment requirement, plus the exact retry key _meta["x402/payment"]. This also resolves the apparent tension with readOnlyHint=false, since the paid retry is a billable side effect rather than a data mutation. It does not mention rate limits, refund/failure behavior, or what the heatmap contains.

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?

Purpose is front-loaded in the first sentence, with payment mechanics and the HTTP equivalent following in a single dense sentence each. No filler, though the parenthetical payment instructions are packed tightly enough to be slightly hard to parse.

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 never characterizes the return value (heatmap dimensions, price-bucket structure, time granularity), which is the main thing an agent must guess. Payment and endpoint details are complete, but the response shape is left entirely unexplained for a paid call.

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 description coverage is 100%, so both parameters are already documented (symbol, and hours defaulting to 24). The description adds only that symbol is a path segment; it does not clarify valid symbol formats or hour granularity, 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?

"Fetch the liquidation heatmap for a symbol" gives a specific verb and resource, and the URL template confirms the exact resource path. It does not explicitly distinguish itself from the closely named sibling funding_funding (funding rates), leaving that separation to inference.

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 description explains the payment handshake flow (call unpaid to get the challenge, then retry with the payment), which is real usage guidance for invoking it. It never says when to prefer this over funding_funding or other funding tools, and gives no guidance on choosing an 'hours' window.

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