get_gas_price

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

No annotations are provided, so the description carries the full burden. It fully discloses the return values (three tiers, base fee, last block, estimated ETH cost) and units (Gwei), as well as the data source (Etherscan oracle). It implies a read-only, non-destructive operation with no side effects, which is appropriate.

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 concise, with three sentences each serving a distinct purpose: stating the function, detailing the output, and providing usage guidance. No extraneous information is included, making it easy for an AI agent to parse and act upon.

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 no parameters and no output schema, the description comprehensively explains what the tool returns and when to use it. It could optionally mention potential errors or rate limits, but the current level of detail is adequate for a simple read operation.

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?

With zero parameters and 100% schema coverage, the description adds value by explaining the meaning of the output fields that are not present in the schema. The enumeration of tiers and their labels provides practical context beyond the empty input schema.

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 gets current Ethereum gas prices from the Etherscan oracle, listing three tiers with descriptive labels (turtle, car, rocket). This verb+resource combination is distinct from sibling tools like get_contract_abi or get_transaction, which serve different purposes.

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 explicitly recommends using the tool before sending any transaction to set appropriate gas, providing clear usage context. While it doesn't mention when not to use it or alternative tools, the guidance is sufficient for a simple read tool.

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