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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds meaningful behavioral context beyond that: pay-per-call pricing, free failed calls, first 25 free, payment via x402 USDC or card key, and that repeated calls are not free. It still omits rate limits, latency, and data freshness.

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 description is front-loaded with purpose and output scope, then usage, example, pricing, and safety. The first sentence is long but each listed data category earns its place; minor redundancy exists around read-only behavior and billing.

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 single-coin research tool with no output schema, the description does a good job enumerating returned data categories and disclosing billing and safety behavior. It would be stronger with explicit sibling alternatives and a hint at response shape or data freshness.

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 single `coin` parameter is already documented as a symbol with a BTC default. The description adds only an example (`coin=ETH`) and the scope of single-coin Hyperliquid research, which is useful but does not substantially deepen parameter semantics.

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 verb and resource: research a single Hyperliquid-traded coin. It enumerates the data returned (price, funding, depth, technicals, sentiment), making the purpose clear. However, it does not explicitly name or differentiate itself from sibling tools such as hyperliquid_indicators, pack_crypto_market, or token_report.

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 clear use case: 'Use before a trade or for a coin brief,' and provides an example call (coin=ETH). It does not state when not to use it or name alternatives for narrower tasks, so it stops short of full routing guidance.

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