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

Annotations only say readOnly, openWorld, non-idempotent, non-destructive; the description adds price per call, a free tier, that failed calls are free, that a malformed address returns 400 uncharged, and that repeat calls are billed. That cost/non-idempotency detail is the key operational fact beyond the annotations and is consistent with idempotentHint=false.

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 purpose, then alternatives, then error behavior, then pricing — logical order with no filler sentences. It is dense with billing/marketing detail ($0.01/call, x402 USDC, card key, 25 free), which is largely relevant but makes the block longer than strictly necessary.

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 covers purpose, alternatives, input format, error behavior, cost, and unit of return. Nothing an agent needs in order to invoke it correctly or budget for it 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 address parameter, so the baseline is 3. The description still adds value by specifying the 0x format expectation, rejecting malformed input with a 400, and giving a concrete example address.

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 (native HYPE balance via eth_getBalance), the chain (HyperEVM), the block (latest), and the units returned (wei and HYPE). It also names what it is not — ERC-20 tokens (hyperevm_token_balance) and aggregate holdings (wallet_portfolio) — so an agent can separate it from the many sibling balance tools without opening schemas.

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 an explicit use case (check whether a wallet can pay gas or a transfer) and names two alternatives with the conditions that select them. That is exactly the when-to-use routing this crowded namespace needs.

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