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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses two non-obvious behavioral facts: the tool is deterministic with no LLM involved, and it is a paid call ($0.001 USDC on Base) requiring a payment passed in _meta["x402/payment"]. It does not say what happens if payment is missing or invalid, which keeps it short of 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?

The purpose and chain scope are front-loaded in the first sentence, with cost and payment mechanics last. The inline JSON example is somewhat lengthy but earns its place because no output schema exists.

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 single-optional-parameter read tool, the description covers what it returns (via the example payload), which chains it covers, that results are deterministic, and how payment works. There is no output schema, yet the sample output substitutes for one adequately.

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?

There is only one parameter and schema coverage is 100%; the schema already lists base/ethereum/arbitrum/optimism, and the description merely restates that chain set and the default. Under the high-coverage rule this lands at the baseline of 3 with no added syntax or constraint detail.

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 opens with a specific verb-and-resource pairing ('Gas price and fee estimate') and immediately enumerates the exact returned fields (gasPrice, baseFee, priorityFee, EIP-1559 maxFee, transfer cost). It also scopes the supported chains, which cleanly separates it from siblings like evm_block or token_price.

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?

It states the supported chains and that 'base' is the default, which implies the intended usage context (estimating transaction fees on a given EVM chain). However, it never says when to prefer this over a sibling such as evm_block, nor any exclusion or prerequisite for calling it.

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