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 and side-effect profile is covered structurally. The description adds the tx_type enumeration and the 'explicit gas / compute units' override path, but says nothing about pricing source, freshness, or currency of the result. With annotations carrying the safety profile, a 3 is warranted.

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 front-loaded sentence that enumerates the key dimensions without padding. It is appropriately sized, though the parenthetical enum list is slightly redundant with the schema and adds length without new meaning.

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?

There is no output schema, so the description should explain what comes back (cost denomination, native token vs USD, whether it is an estimate range). It explains nothing about the return value, and with only 25% schema coverage on four parameters the definition leaves an agent guessing about the result shape.

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 only 25%, so the description must compensate. It does list the tx_type values and clarify the gas_units override ('gas units (EVM) or compute units (Solana)'), but it merely repeats enum members already in the schema and adds no meaning for 'speed' tiers or chain-specific behavior, leaving the coverage gap only partly filled.

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 states a specific resource and scope: the cost of one transaction on a chain at a given speed tier, parameterized by tx type or explicit units. That is enough to distinguish it from gas_now and cheapest_chain_to_deploy in spirit, though it never names those siblings or explicitly contrasts the per-transaction view with them.

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 guidance. The phrase 'one transaction on a chain at a speed tier' implies the estimation scenario, but it never says when to prefer this over gas_now (live gas prices) or cheapest_chain_to_deploy (cross-chain comparison), nor does it state prerequisites.

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