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

Goes well beyond the annotations by disclosing that queries hit third-party public RPC servers, the precise billing rule (charged only if at least one network answers; not charged on Base when all RPCs fail or input is bad), the x402/USDC-on-Base payment rail, and a terms link. A non-idempotent, open-world read with real payment consequences is fully disclosed.

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-loads what the tool returns and keeps the network default early; the payout/terms detail is dense semicolon-chained prose but each clause carries operational weight. Slightly heavy for a one-parameter tool, yet nothing is truly wasted.

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, the description compensates by naming every returned field (chainId, height, headTime, headAgeSeconds, finalizedHeight, finalityGap) and clarifying the per-chain meaning of finality. Billing, defaults, and payment rail are also covered, leaving no material gap for correct invocation.

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 'network' parameter is already documented, including the CAIP-2 alternative. The description's 'comma list; default all five' restates the schema rather than adding syntax examples or behavior for mixed/invalid network entries. Baseline 3.

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 resource (current block number / slot / ledger index) and enumerates the five chains covered, which is enough to distinguish it from siblings like gas, balance, and tx_status. An agent knows exactly what it gets back without opening the schema.

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 explains the network parameter's default ('all five') and billing trigger, which implies usage, but never says when to pick this over gas/balance/tx_status or when a narrower per-chain call is preferable. No explicit exclusions or alternatives are named.

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