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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description's 'reads or computes only and changes nothing' largely restates them. It does add genuinely new context: 404 on nonexistent blocks is uncharged, and every call is billed so repeats are not free. Pricing detail is useful but is commercial rather than operational behavior.

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 core purpose, returned fields, alternative tool, and error behavior are all front-loaded. The trailing pricing/free-tier sentence is dense and somewhat boilerplate-heavy, but it is not padding for a paid x402 tool.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so (hash, timestamp, transaction count, gas used and limit, base fee in gwei, producer). Combined with error semantics, cost, and the sibling pointer, nothing an agent needs to invoke it correctly is missing.

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% and the single parameter already documents 'Block number, or latest (default)'. The description still adds value by specifying the number must be decimal and giving a concrete example ('number=latest'), which clarifies format beyond the schema text.

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 and resource (fetch latest block number or any block by decimal number on Base) and enumerates the returned fields. It also explicitly distinguishes itself from base_gas, so an agent can separate it from the many sibling *block/base_* tools.

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?

Gives concrete when-to-use guidance ('Use for timestamps and confirmation counts') and names the alternative for a different need ('for current fees use base_gas'). It also notes the default/example input ('number=latest') and the not-yet-mined 404 case, leaving little to inference.

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