get_gas_fees

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read-only operation ('Get current...') but does not elaborate on data freshness, rate limits, or any side effects. It is minimal but sufficient for a zero-parameter, read-only tool.

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 a single concise sentence that front-loads the key action and result. Every word is valuable with no redundancy.

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 the tool has zero parameters, no output schema, and is relatively simple, the description fully covers what the tool does and what it returns. Sibling tools provide enough context to differentiate, making this description complete.

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?

There are no parameters in the input schema, so baseline score is 4. The description does not need to add parameter information, and it appropriately focuses on the output (fast/standard/slow in Gwei).

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 verb 'Get', the resource 'current Ethereum gas fees', and specifies the output format 'fast/standard/slow in Gwei'. It distinctly sets this tool apart from sibling tools like get_token_price, get_fear_greed, etc., which cover different crypto metrics.

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 implies usage for fetching gas fees but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites, caveats, or exclusions. It is adequate but lacks explicit direction.

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