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

Annotations only say read-only/non-destructive; the description adds substantial extra context: takes no input, billed per call via x402 USDC or card key, first 25 free, failed calls free, and repeats are not free because each call is charged. That charging/idempotency nuance is precisely what an agent needs before deciding to re-call.

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?

Front-loaded with the return payload, then usage routing, then pricing caveats. Efficient and every sentence earns its place, though the billing sentence is dense enough that it could be tightened slightly.

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?

For a no-input, read-only tool with no output schema, the description enumerates the returned fields and the derived transfer-cost figure, plus cost and idempotency behavior. Nothing an agent needs to call or interpret it is missing.

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?

Zero parameters with 100% schema coverage, so there is nothing to disambiguate and the baseline is 4. The description correctly reinforces 'takes no input' rather than inventing parameter guidance.

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+resource (get current gas on Optimism) and enumerates exactly what it returns: gas price, base fee, suggested priority fee in gwei, and the cost of a plain 21,000-gas ETH transfer. It also contrasts itself with op_receipt for historical actual fees, so an agent can route correctly without reading schemas.

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?

Explicitly says when to use it ('before sending a transaction or to decide whether to wait') and names the alternative for the adjacent case ('for the fee a past transaction actually paid use op_receipt'). This is the when/when-not/alternative pattern at full strength.

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