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

With no annotations, the description carries the burden and does well: it discloses the paid, metered nature of the call (0.001 USDC per call over x402 on Base), which is exactly the kind of cost/auth context an agent needs before invoking. What it omits is freshness/caching behavior (is the gas price live or cached?) and whether the payment requires prior setup, which keeps it from a 5.

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?

Three short sentences: what it returns, when to use it, what it costs. Front-loaded with the payload description and zero filler; each sentence earns its place.

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 properly enumerates the return values (base fee, priority fee, block) and specifies units (gwei). It is complete enough to call correctly; the only real gap is the interaction between the fixed "Base" wording and the `chain` parameter, plus lack of data-freshness guidance.

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% for the single optional `chain` parameter, so the baseline is 3. The description phrase "on Base" implies Base is the supported/default chain, which adds a little meaning over the schema's terse "Example: base", but it never says whether other chains are accepted or what happens if `chain` is omitted.

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?

The description names a precise resource (gas price on Base, in gwei) and enumerates the returned components: base fee, priority fee, and the block it was read at. This is unmistakably distinct from every sibling (evm_block, evm_balance, evm_tx, etc.), so an agent can select it without opening the 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?

"Use it to estimate gas fees before sending a transaction" gives a clear triggering context. There are no explicit exclusions or named alternatives, but no sibling is a plausible substitute for gas estimation, so the guidance is sufficient in practice.

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