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

No annotations are provided, so the description carries the full burden. It does disclose two useful traits beyond the schema: the paid cost (50000 atomic USDC) and that it uses the public API without keys. It omits rate limits, read-only/reversibility framing, and latency or caching 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?

A single dense sentence that front-loads the cost and then enumerates the payload. No filler, though the trailing field list duplicates what the output schema already conveys.

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?

One optional parameter with full schema coverage plus an output schema means return values need not be explained, and the tool is otherwise well-specified for its complexity. The only real gap is the undifferentiated overlap with the funding_snapshot sibling.

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 coverage is 100% for the single coin parameter, including the XBT→BTC / WETH→ETH normalization note, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what the schema already documents, matching the baseline 3.

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: a Hyperliquid perpetual funding snapshot with an enumerated payload. However, a sibling named funding_snapshot exists and the description never explains how hl_funding_snapshot differs from it, so sibling differentiation is missing.

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 price tag ($0.05 USDC) implies this is a paid alternative to a free sibling, but the description gives no explicit when-to-use-this-vs-funding_snapshot guidance. Nothing about when the paid call is warranted over the free path.

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