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

Annotations already establish readOnlyHint and openWorldHint, and the description adds meaningful operational context: latency under a minute, coverage limited to ~420 large accounts rather than all positions, and a 1.1 USDC per-call x402 payment requirement. It is transparent about cost and data limitations, though it does not describe output shape or failure behavior.

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?

The first sentence is well front-loaded and informative, but the description is bloated by promotional identity verification, token fee details, wallet addresses, and endpoint URLs that do not help an agent decide to invoke the tool. Much of the latter half does not earn its place in a tool definition.

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?

There is no output schema, but the description explains the returned concept (estimated liquidation levels in % buckets, biggest clusters highlighted), the data source limitation, latency, and payment requirement. That is enough for correct invocation, with only return-field structure left vague.

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 the schema already documents asset, rangePct, and bucketPct including defaults and bounds. The description repeats the parameter names and gives one example, but adds no semantics beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific resource and output: estimated long and short liquidation levels in % buckets around a Hyperliquid perp's mark price, with biggest clusters highlighted. It is clearly distinguishable in substance from siblings like hl_funding_snapshot or hl_smart_money, but it never names or routes against those alternatives, so it falls short of a 5.

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 implied through the input example and the note that results come from ~420 large accounts, but there is no explicit when-to-use guidance or comparison to alternative liquidation/smart-money tools. An agent can infer the use case, but selection guidance is thin.

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