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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new behavioral context by disclosing a paid endpoint ($0.002 USDC on Base via x402), which an agent must know before invoking. It still omits whether estimation can fail or how the quote is priced, but the cost disclosure is real added value beyond the annotations.

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 short sentences, zero waste, with the core action front-loaded and the pricing note trailing. Every 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?

For a 4-parameter tool with no output schema and 0% schema description coverage, the description should at minimum clarify the transaction inputs it estimates for. It covers purpose and payment model but leaves parameter meaning and the shape of the estimate unexplained; annotations only partially fill the gap.

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 description coverage is 0% and the description never mentions 'to', 'from', 'data', or 'value'. It cannot compensate for the gap: an agent gets no meaning for the required 'to'/'from' fields or the optional calldata/value fields beyond their type patterns.

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+resource ('Estimate gas and the USD cost of a Base transaction') with a clear scope qualifier ('before signing it'). It implicitly differentiates from the sibling base_gas by adding the USD cost dimension, but never names or contrasts with that sibling, so differentiation is left to inference.

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?

'before signing it' gives a rough usage context, implying pre-transaction estimation. However it does not say when to prefer this over base_gas or base_call, nor does it state prerequisites or exclusions. Usage is implied rather than stated.

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