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

Beyond the readOnly/openWorld annotations, the description adds materially new behavior: deterministic output with no LLM involvement, a concrete price ($0.001 USDC on Base), and the exact payment plumbing (_meta["x402/payment"]). These are things an agent must know before calling and cannot get from annotations or schema. It does not cover failure behavior for invalid block numbers.

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?

Purpose is front-loaded in the first sentence, followed by return fields, then payment terms. The embedded example JSON is verbose but justified since there is no output schema. Every sentence carries information; no filler.

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?

With no output schema, including a full sample response object (chain, number, hash, timestamp, iso, txCount, gasUsed, gasLimit, baseFeeGwei) is the right compensation, and the paid-call mechanics are spelled out. Minor gaps remain around error handling and what 'deterministic, no LLM' implies for caching, but nothing blocking prevents a correct call.

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 both parameters (chain enum, block number) are already fully documented in the schema. The description restates the chain list and the 'latest' default without adding format or edge-case meaning. Baseline 3 applies.

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?

Opening sentence states a specific resource and retrieval mode (latest block or by number), and the second sentence enumerates exactly what is returned across four named chains. It reads clearly as a block-fetch tool, though it never explicitly distinguishes itself from the sibling evm_gas, which covers overlapping gas/base-fee territory.

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?

Usage is only implied: 'latest block or block by number' plus the default of 'latest'. There is no statement of when to prefer this over evm_gas, base_tx_status, or ai_tx_explain, and no exclusion conditions. An agent must infer the routing decision from sibling names alone.

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