calculate_gas_fee_eth

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

No annotations are provided, so the description must fully disclose behavior. It only states the tool calculates gas fees, but does not mention that it is a read-only, non-destructive operation, nor does it explain the calculation formula or assumptions like default values. This is insufficient for a tool with no annotations.

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?

The description is extremely concise with two short sentences that convey the core purpose and a helpful pointer to related tools. Every word contributes value, and there is no unnecessary information.

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?

Given that there is an output schema (though not provided in the input), the description mentions the output in ETH and USD, which likely matches. However, it does not explain the calculation logic, default values for parameters, or any limitations. For a simple calculator with three parameters and a small description, it is minimally adequate but lacks completeness.

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 input schema already describes all three parameters with minimums, defaults, and descriptions. The tool description does not add any additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the tool calculates Ethereum transaction gas fees in ETH and USD, using a specific verb and resource. It distinguishes itself from sibling tools by focusing on a specific cryptocurrency calculation, and even directs users to list_bundles for related crypto calculators.

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?

The description mentions seeing list_bundles for related 'crypto' calculators, implying there are related tools, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. No prerequisites or exclusions are mentioned.

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