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

Goes well past the annotations: discloses pricing ($0.002/call via x402 USDC or card key, first 25 free, failed calls free) and that each call is charged so repeats are not free -- which explains the otherwise puzzling idempotentHint=false. It also confirms 'reads or computes only and changes nothing', consistent with readOnlyHint=true. Cost and billing behavior is exactly the kind of operational detail annotations cannot convey.

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-loads the resource and chain, then the returned fields, then usage, then cost -- a sensible priority order with no filler sentences. It is on the long side because the return-field enumeration and the billing caveats are both spelled out, but each sentence carries information an agent needs.

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 usefully enumerates units (gwei vs wei) and the concrete computed values returned. Combined with the stated safety profile (read-only, no side effects) and the billing model, an agent has everything needed to call this correctly and predict the cost.

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?

Only one optional parameter (`only`), and the schema description already covers it at 100% with an example and fallback behavior. The description says nothing about `only` or the result-key projection it enables, so it adds no meaning beyond the schema. Baseline 3 applies when the schema does the full job.

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 concrete verb and resource -- live gas prices read from the latest Base block (chain 8453) -- and enumerates exactly what is returned (base fee, priority fee in gwei, maxFeePerGas/maxPriorityFeePerGas in wei, block fullness, ETH/ERC-20 transfer fee estimates). This lets an agent separate it from base_estimate_gas (per-transaction estimation) and base_gas_history (historical series) 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?

Explicit timing guidance: 'Use before sending a transaction on Base or to decide whether to wait for lower fees.' That is a clear use context with no exclusions. It stops short of naming the sibling alternatives (base_estimate_gas, base_gas_history, pack_gas_tracker) or stating when not to use it, so it lands at 4 rather than 5.

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