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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds substantive context annotations cannot: this is a x402-metered call costing 0.01 USDC, settled on five named chains. That payment/authorization requirement is exactly the kind of operational fact an agent must know before invoking. It omits data freshness/caching and any rate limit, hence not a 5.

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?

A single dense sentence that front-loads what is returned and closes with the cost, which is the one fact an agent might otherwise discover only after failing. No filler, no restatement of the title.

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?

An output schema exists, so return-shape explanation is not required; the description nonetheless summarises the metrics, which helps selection. Cost and chain coverage are disclosed. What is missing is sibling disambiguation in a namespace crowded with liquidation tools and any note on update cadence for the 1h/24h windows.

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?

The tool takes zero parameters, so the schema has nothing to document and the baseline is 4. The description correctly does not invent parameters, and instead spends its words on the fixed dimensions of the response (windows, split, exchange breakout) — the right allocation for a no-arg call.

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+resource and enumerates the exact payload: 1h/24h totals, longs vs shorts USD split, biggest print, per-exchange breakout for the five named majors. That scoping ('the 5 majors') is genuinely differentiating. It stops short of naming which sibling it displaces, so an agent still has to guess between this and get_liq_pulse / get_liquidation_leaders / get_liq_feed.

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?

Usage is only implied: the coverage/resolution described (aggregate 1h/24h windows on majors) hints at a summary use case, but there is no explicit 'use this instead of X when Y' and no exclusions against the eight other liquidation siblings. The cost disclosure ('0.01 USDC per call') does usefully signal a paid-vs-free routing decision, which is closer to guidance than most tools get.

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