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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context: it returns cost in both ETH and USD, and it is a paid call at $0.002 USDC on Base via x402 — a billing detail no annotation conveys.

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 tight sentences, front-loaded with the core purpose and ending with pricing. Nothing is padded, though the input clause is ambiguous in a way that costs clarity rather than saving space.

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?

With no output schema, the description does name what comes back (gas, ETH cost, USD cost), and it discloses the payment model. It is close to complete for a simple estimation tool, with the required/optional input mismatch being the main 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 coverage is 0%, so the description carries the full burden, and it only lists parameter names. Worse, it says 'to, and optionally from, data and value' while the schema marks both 'to' and 'from' as required, which can mislead the agent about what it must supply. No format or unit guidance (hex addresses, value denomination) is given.

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: estimating gas plus ETH/USD cost for a Base transaction, and scopes it to 'before signing it'. This distinguishes it from network-level siblings like base_gas, though it never names an alternative explicitly.

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?

The phrase 'before signing it' implies the pre-flight use case, which is real guidance. However, it never states when to prefer this over base_gas, base_call, or base_receipt, nor any exclusions or prerequisites.

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