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

Beyond readOnlyHint/openWorldHint, it discloses the billing model (3 free calls/day across all tools, then $0.0015 USDC via x402 or card credits, paid in-band through params._meta['x402/payment']) and the data source ('public RPC nodes with failover; no keys'). The no-keys and failover notes tell the agent there is no auth step and that failures are handled upstream.

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?

Two tight sentences carry purpose, scope, return contents, and the alternative, with no filler. The only structural weakness is that the pricing/payment preamble precedes the purpose statement, so the core capability is not fully front-loaded.

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 read-only, zero-required-param tool with an output schema already present, the description supplies everything an agent needs: what it returns, which chains, the routing alternative, auth requirements, and cost implications of calling it.

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% on the single 'chains' parameter, so the schema already defines the accepted values. The description names the five chains but adds no syntax or default guidance beyond what the schema states. Baseline 3 applies.

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 and resource: live gas prices across 5 named EVM chains, with the exact per-chain payload (gwei, latest block, transfer/swap cost in native and USD, cheapest-chain ranking). It explicitly distinguishes itself from the sibling base_gas (Base only).

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?

Contains an explicit 'When to use' clause covering both jobs (pick the cheapest chain, price a transfer/swap) and names the alternative with its exclusion: 'Use base-gas for Base only.' Nothing is left to inference.

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