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

Goes well beyond the readOnlyHint annotation by disclosing cost ($0.01/call via x402 USDC or card key), a free tier (first 25), free failed calls, and that repeats are charged — which explains the idempotentHint=false. 'Reads or computes only and changes nothing' restates the safety profile rather than contradicting it, and covers Hyperliquid-only scope.

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?

Front-loaded with the core purpose and the returned data before cost detail, and every sentence carries usable information (scope, use case, example, pricing). The second sentence is a long comma-run list of indicators, which is dense but still scannable.

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?

With no output schema, the description carries the return-value burden and does so by enumerating each data category the agent receives. Pricing, free tier, failure behavior and read-only nature are all stated, so nothing an agent needs before calling is missing.

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% and already documents the single 'coin' param including its default of BTC. The description only adds an example value (coin=ETH) and the note that ~200 symbols beyond BTC/ETH/SOL/HYPE exist, which is marginal beyond the schema.

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?

Specific verb + resource + scope: 'research a single coin traded on Hyperliquid' with an explicit enumeration of the returned data (price, OI, funding, depth, 4h/daily technicals, sentiment). It is clearly an aggregator of the hyperliquid_* siblings, but it never names them, so the distinction from hyperliquid_market / hyperliquid_indicators / pack_crypto_market must be inferred.

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?

Gives a use case ('Use before a trade or for a coin brief') and an example ('coin=ETH'), which is enough to know when it fits. But it offers no when-not guidance and never contrasts with the dozens of single-purpose hyperliquid_* or pack_* siblings an agent must choose between.

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