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

Annotations already establish read-only and open-world behavior; the description adds meaningful context by disclosing the 0.10 USDC cost and disclaiming financial advice. It does not fully explain result behavior, but the read-only annotation lowers the burden and the cost/disclaimer are genuinely informative beyond the schema.

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 extremely concise and front-loaded: 'gas oracle' immediately identifies the domain, then scope, options, pricing, and disclaimer follow. Every phrase serves a purpose; the lack of illustrations or filler bloats no size.

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?

Description is adequate for a simple read-only tool with one optional enum parameter, but there is no output schema and the description does not explicitly state what the returned gas data looks like. 'Gas oracle' implies the data shape, and the cost is clear, but an agent calling blindly still has uncertainty about return format.

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 enum network parameters are already well documented; the description's 'Optional network' adds little beyond the schema. The description does advertise the dual network concept, which explains the enum, but does not delve into defaults or rail-specific output differences.

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 identifies a specific resource, a gas oracle, and its supported rails (BSC+Base), which is enough to distinguish it from the listed siblings. It stops short of a 5 because it has no explicit verb stating what the tool returns, so 'oracle' still implies the behavior rather than stating it.

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?

There is no guidance about when to use this tool versus alternatives, nor any exclusion such as 'use native_balance instead for wallet balances.' The optional-network note is useful but describes input selection, not when to pick this tool over a sibling.

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