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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations do not: units (gwei), the specific returned fields, and the freshness basis (last 20 blocks).

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?

A single sentence that is fully front-loaded: resource, units, and return breakdown all appear before any ellipsis could be needed. No filler words.

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 must describe return values, and it does (base fee and four tier levels). The only shortfall is that the chain parameter's default and supported values live solely in the schema enum, so an agent must still open the schema to know the input surface.

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?

The schema has 0% description coverage, so the description carries some burden, but it never mentions the 'chain' parameter, its default of ethereum, or which chains are supported. The enum values are largely self-explanatory, so the description's implied 'EVM chain' framing adds only marginal value.

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 names a specific resource (gas price on an EVM chain) and even details the return shape (base fee plus slow/standard/fast/instant tiers), which is more than a restatement of the name. It does not explicitly distinguish itself from siblings like get_network_fees or get_bitcoin_fees, so it stops short of a 5.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named. The word 'Live' faintly implies real-time queries, but nothing tells the agent how this differs from get_network_fees or when to prefer one over the other.

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