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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: freshness ('straight off the node'), ordering ('newest first'), and the crucial data-model caveat that one liquidation can span several fills sharing an order id, which affects counting/dedup.

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, front-loaded with the resource and its ordering, then the one non-obvious data caveat. No filler and nothing redundant with the schema.

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?

No output schema exists, so the description usefully sketches the return shape (who, market, size, price). Safety is covered by annotations, but the undocumented hours and limit parameters and any pagination/truncation behavior are not addressed, leaving a small gap for a 5-parameter filter tool.

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 60%: coin, side and min_usd are documented in the schema, while hours and limit have no descriptions at all. The description adds no parameter-level meaning (no defaults, no units, no filtering semantics beyond what the schema titles carry), so it neither compensates for the gap nor earns above baseline.

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 with granularity and ordering: 'individual Hyperliquid liquidation fills, newest first'. The word 'individual' implicitly distinguishes it from aggregate siblings like liquidation_totals and liquidation_map, so an agent can route without opening a 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?

The granularity hint ('individual ... fills') implies this is the per-fill alternative to the aggregate liquidation tools, but no sibling is named and no when/when-not condition is given. Usage must be inferred from the contrast in scope.

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