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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that both ETH and USD figures are returned, which is thin and partly redundant with the output schema; no mention of defaults or assumptions (e.g. default gas limit/ETH price) at the behavioral level.

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?

Two short sentences, front-loaded with the core purpose and followed by a single relevant discovery pointer. No filler, no restating of the title.

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 a full output schema and 100% schema coverage, the description needn't explain parameters or return values, and it names the resource and output units. What is missing is only minor: which gas-price/limit conventions or defaults apply when an agent omits optional inputs, which the schema already handles via defaults.

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 all three parameters (gas_limit, eth_price_usd, gas_price_gwei) are already documented with units, defaults and minimums in the schema. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 (Calculate) and a precise resource (Ethereum transaction gas fee) plus the unit of the result (ETH and USD). This clearly distinguishes it from the hundreds of sibling calculators, none of which share this resource.

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?

Usage is only implied: an agent infers it should call this when it wants an ETH gas-fee estimate. The pointer to list_bundles is a discovery aid for related crypto calculators rather than a when-to-use/when-not rule or an explicit alternative for the same task.

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