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

With no annotations, the description carries the full burden. It does disclose cost and access ('$0.005 via x402') and the output shape, which is valuable. It stops short of stating read-only status, rate limits, or failure behavior, so it only partially covers the behavioral profile.

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 cost and purpose, then outputs, then the sibling contrast, then supported chains. Sentences are informative and mostly earn their place, though the 'single gas number' sentence leans slightly rhetorical.

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?

No output schema exists, so the description usefully describes return content (trend, percentiles, utilization, recommendations). It covers the primary parameters adequately but leaves x_payment unexplained, a minor gap for a 3-param tool.

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 67%. The description repeats the chain list already given in the schema and mentions 'N blocks' matching the blocks param, adding no syntax beyond the schema. The x_payment parameter remains undocumented in both description and schema, leaving a gap.

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 (EIP-1559 fee history) and enumerates the concrete outputs: base-fee trend, priority-fee percentiles, mean block utilization, and recommended maxFeePerGas/maxPriorityFeePerGas. It also distinguishes itself from sibling chain_gas_price by contrasting 'a single gas number' with trend capability.

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 line 'A single gas number cannot tell you whether fees are rising; this can' clearly signals when to reach for this tool over chain_gas_price or chain_estimate_gas. However, there is no explicit when-not guidance or statement of prerequisites beyond the payment note.

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