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

Goes beyond the annotations by explaining the counterintuitive readOnlyHint=false ('Reads or computes only; not marked read-only because each call is charged'), and adds pricing and failure semantics ($0.003/call via x402 USDC or card key, first 25 free, failed calls free) that no structured field carries. This resolves a potential annotation misread, though it does not describe freshness/latency of the gas quote.

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 routing, then billing caveats — a sensible order with no filler sentences. It is a dense single paragraph packing several distinct concerns, so slightly less scannable than it could be, but nothing is wasted.

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?

There is no output schema, so the description carries the return-value burden and does so fully (which fields, what units, plus a concrete derived figure). For a no-input, no-annotation-help tool, an agent has everything needed to call it and interpret the result.

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?

Zero-parameter tool, so the baseline is 4. The description's 'Takes no input' is accurate and consistent with the empty schema, but adds nothing the schema does not already show.

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 ('Get current gas on Ethereum') and enumerates exactly what is returned: gas price, base fee, suggested priority fee in gwei, plus the cost of a 21,000-gas ETH transfer. It is clearly distinguishable from the sibling gas tools on other chains (arb_gas, base_gas, op_gas) and from eth_receipt, which it names.

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 explicit when-to-use guidance ('Use before sending a transaction or to decide whether to wait') and an explicit when-not/alternative ('for the fee a past transaction actually paid use eth_receipt'). An agent can route correctly without opening any schema.

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