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

With no annotations at all, the description carries the full behavioral burden and does more than most: it discloses the data source (Hyperliquid), the returned payload, the pull-direction signal, and a per-call price of $0.007. Gaps remain — it never states freshness/latency of the clusters, whether the call is purely read-only, or what happens when no clusters exist near price.

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?

One dense sentence with the price front-loaded and the use case before the mechanics; nothing is padding. The em-dash chaining makes it slightly harder to parse than it needs to be, and the param note is 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?

For a one-parameter read tool with no output schema, the description supplies the output shape (distance %, notional, direction), the venue, and the cost — enough for an agent to call it correctly. Missing freshness and empty-result behavior are the only notable omissions.

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 single parameter is fully documented by the schema (100% coverage, enum of six coins with a BTC default), and the description merely restates "coin (default BTC)". It adds no meaning such as whether all six symbols have Hyperliquid perp coverage or how the default behaves. Baseline 3 applies when the schema does the work.

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?

"Finding the nearest Hyperliquid liquidation clusters above and below price" is a specific verb+resource with scope, and the fields returned (distance %, notional size, pull direction) sharpen the picture. It doesn't explicitly contrast itself with the sibling liquidation_pressure, so it stops short of 5, but the use case framing (placing TPs/stops) makes the distinction inferable.

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?

It gives a concrete when-to-use: placing take-profits and stops, specifically to avoid parking a stop inside a liquidation cluster. That is actionable context rather than a generic blurb. No explicit when-not-to-use or named alternative tool, so it is not a 5.

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