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

The readOnlyHint annotation already indicates this is a safe read; the description goes beyond that by adding the 10-second cache, the point-in-time/change-every-block caveat, and the rough-heuristic limitation on USD figures. That is meaningful context an agent needs before acting on the output. A small deduction because the description does not explicitly mention rate limits or error behavior, but those are not critical for a read-only gas price 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?

The description is tight and front-loaded: the first sentence states what the tool returns, the second gives use guidance, and the third lists limitations and alternatives. Every sentence earns its place; there is no filler or redundant restatement of the tool name.

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 read-only tool with only two optional parameters, a 100%-coverage schema, and an output schema present, the description is complete enough: it covers purpose, usage timing, cache behavior, limitations, and alternatives. The only small gap is the absence of explicit error/edge-case behavior (e.g., unsupported chain handling), which is minor and not essential for correct invocation.

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 schema already explains both parameters. The description adds value by clarifying how include_usd_estimate is used (rough heuristics at 21k/150k gas) and by stating the cache implication (repeated calls are wasteful), which goes beyond simply restating the 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 names a specific resource (EIP-1559 gas fees on Ethereum/Base) and identifies the concrete data returned: base fee, priority fee, next-block estimate, and congestion thresholds. It also explicitly scopes the tool by chain (Ethereum and Base only) and by what it is not (an execution quote). This distinguishes it from the sibling tools get_block and get_dex_quote without needing to inspect their 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?

The description gives explicit when-to-use guidance ('Use before advising a transaction') and when-not-to (calls are pointless within the 10-second cache). It also names the alternatives (get_block, get_dex_quote) to divert the agent appropriately. No exclusion is left to inference.

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