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

Goes well past the annotations: it discloses per-call billing ($0.01 via x402 USDC or card key, first 25 free, failed calls free) and that repeated calls are charged, which is exactly why idempotentHint is false. It also restates the read-only, no-mutation nature in operational terms ('reads or computes only and changes nothing'), adding billing/auth context annotations cannot carry.

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 returned values, then usage, then billing — a sensible order with no filler sentences. It is on the dense side and the price/credits clause is commercial rather than operational, but it does carry real decision value about repeat calls.

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?

No output schema exists, and the description compensates fully by naming the returned fields and the practical transfer-cost figure. The only gap is the unmentioned `only` parameter, which the description actively contradicts with 'Takes no input' rather than merely omitting.

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 the description says 'Takes no input', but the schema actually exposes an optional `only` filter for trimming result keys. That statement is simply wrong about the tool's surface and could lead an agent to never use the projection parameter, which is the one option available for controlling response size.

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 ('Current gas price on HyperEVM', eth_gasPrice) and enumerates exactly what is returned: gas price, base fee, suggested priority fee in gwei, and the cost of a 21,000-gas HYPE transfer. That return content plus the explicit contrast with hyperevm_receipt lets an agent separate it from the gas_history, estimate_gas and receipt siblings without opening any schema.

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 clear positive context ('use before sending a transaction or to decide whether to wait') and names an explicit alternative with its selection condition ('for the fee a past transaction actually paid use hyperevm_receipt'). It omits the two other nearby confusables, hyperevm_gas_history and hyperevm_estimate_gas, so the routing map is clear but not complete.

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