get_gas

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

No annotations are provided, so the description carries the burden. It clearly states the tool returns data ('Returns gas price in gwei') and emphasizes 'Live gas prices', indicating a read-only, informational operation with no destructive side effects mentioned.

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 repeats the same sentence structure twice (listing gwei, base fee, and USD costs), making it more verbose than necessary. It could be trimmed to a single clear statement without losing 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?

Despite lacking an output schema, the description enumerates the exact returned fields (gas price in gwei, base fee, USD costs for transfer/ERC-20/swap) and the ordering behavior, giving an agent sufficient context to correctly use the tool and interpret results.

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 covers 100% of parameters with an enum and description. The description adds value by clarifying that omitting the chain defaults to 'all' and that results are ranked cheapest-first, enhancing the schema's basic enum listing.

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 retrieves live gas prices across multiple specific chains (BNB Chain, Polygon, Arbitrum, Base, Avalanche, Optimism) and outputs them ranked cheapest-first, which differentiates it from pricing, liquidity, and venue tools in the sibling list.

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 bridging, routing, and execution timing, but does not explicitly state when to prefer this tool over alternatives like get_token_price or get_slippage. The context is present but could be more direct.

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