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

Goes well beyond the annotations: revert behavior (422 with reason, uncharged), pricing model ($0.01/call via x402 or card key, first 25 free, failed calls free), and the non-idempotent charging caveat for repeats. The only minor gap is no mention of pagination/confirmation depth or eventual consistency, but for a compute-only tool this is rich disclosure.

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 core action and alternative routing before the example and pricing details. Dense but nearly every clause carries information; the pricing/payment sentence is long but operationally relevant given the x402 charge model.

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 compensates by explaining what is returned (gas units, gwei, and MNT cost), the error path, and the charging semantics. An agent has everything needed to call it and interpret the result.

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%, so the baseline is 3; the description adds real value by clarifying units ('value in MNT'), that calldata is for a contract call, and the conditional guidance that 'from' is needed when the call depends on the sender — a nuance absent from the schema.

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 ('Estimate the gas a transaction would use on Mantle'), names the underlying RPC (eth_estimateGas), and explicitly distinguishes itself from the sibling mantle_gas by scope. An agent can separate it from the ~15 other *_estimate_gas and *_gas tools at a glance.

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?

Gives explicit when-to-use ('before sending a transaction or to price a batch') and an explicit alternative ('for the gas price alone use mantle_gas'). Also specifies which inputs to supply and when 'from' matters, leaving nothing to inference.

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