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

With no annotations, the description carries the full behavioral burden, and it only discloses the data content (base + priority fee) and a trial quota of 5 calls per registered wallet. It doesn't disclose supported chains/networks, fee units (wei/gwei), response shape, or what happens when N exceeds available history. The trial-call disclosure is a plus, but significant behavioral gaps remain.

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?

Two sentences, zero filler, with the core purpose front-loaded. The emoji and free-trial note add a genuine operational constraint without much cost. Slightly more structure (e.g., separating the parameters) would be better, but this is appropriately compact.

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 4-parameter blockchain tool with no output schema, no annotations, and no enums, the description is under-specified: it never explains the n/blocks and chain/network relationships, supported values, or return format. The trial-call note is useful but cannot compensate for the missing invocation-critical details.

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 technically 100%, but the schema descriptions are boilerplate tautologies ('N to process', 'Blocks to process') that add no meaning. Critically, the tool has both n and blocks, and both chain and network, and the description never clarifies these apparent redundancies — an agent cannot reliably know whether n or blocks is the block count. The description's 'Last N blocks' hint is not enough to disambiguate.

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 states a specific resource (fee history for the last N blocks) and the data it returns (base fee + priority fee), which distinguishes it from siblings like x402-gas-price (current price) and x402-block-fee (single block fee). It doesn't explicitly name the alternatives it is not, so it stops short of a 5, but the verb+resource+scope are clear.

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 implies a lookback use case ('Last N blocks') but provides no explicit guidance on when to choose this tool over the many fee/gas siblings (x402-fee-estimate, x402-gas-now, x402-block-fee, x402-block-number). There are no exclusions, alternatives named, or conditions. The free-trial note is a quota constraint, not usage routing.

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