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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, and the description adds real context beyond them: pricing ($0.01/call, first 25 free, failed calls free) and the explicit warning that repeats are not free, which explains the idempotentHint=false. It stops short of describing result shape details like units beyond gwei or the freshness/latency of the price, so it is strong but not exhaustive.

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-loaded with purpose, return fields, and usage before pricing boilerplate. The pricing/settlement sentence is longer than the functional content needs, but it carries genuinely decision-relevant cost information, so it earns most of its 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?

No output schema exists, and the description compensates by naming the returned fields and units (gwei) plus a concrete derived figure (21,000-gas transfer cost). Combined with the zero-required-param schema and safety annotations, an agent has everything needed to call it correctly.

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 100%, so the `only` filter is already fully documented in the schema; baseline 3 applies. The description does not mention `only` and instead says 'Takes no input', which is slightly at odds with the optional projection parameter and gives an agent no extra guidance on using it.

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 ('Current gas price on Mantle') and enumerates the returned fields: gas price, base fee, suggested priority fee in gwei, plus the cost of a 21,000-gas MNT transfer. It is clearly distinguishable from mantle_gas_history and mantle_receipt, the latter named explicitly as the historical alternative.

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 triggers ('Use before sending a transaction or to decide whether to wait') and routes the historical-fee case to mantle_receipt. An agent knows both when to call this and when to call something else.

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