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

No annotations are provided, so the description carries the full burden; it does disclose the payload contents (counts, percentiles, top contracts, largest transfers), which is useful. It does not mention that a pending block is a moving snapshot replaced every block, nor any rate limits or auth expectations - real gaps for a no-annotation tool.

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, purpose front-loaded, with the chain list and payload enumeration packed into a single clause. No filler and nothing that could be cut without losing information.

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?

An output schema exists, so return values need not be spelled out, and the description sensibly stops short of that. But with no annotations and an undocumented 'limit' plus no note about snapshot volatility, an agent still lacks what it needs to interpret or tune the 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 0%, so the description must compensate. It partially does by listing the supported chains (Ethereum, Base, Arbitrum, Optimism, Polygon), effectively supplying the enum that the schema omits. However, it never refers to the 'limit' parameter, so the agent cannot tell what it bounds or how it affects the returned transfer/contract lists.

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 ('an EVM chain's pending block') and enumerates exactly what it returns: transaction count, priority-fee and gas-price percentiles, most-called contracts, largest native transfers. That clearly separates it from a generic block or gas tool at the purpose level, though it never names the sibling (evm_block, evm_gas_fees) it supersedes.

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?

'Use to price gas' gives one explicit use case, which is more than nothing. But it offers no when-not guidance and no mention of the obvious alternatives (evm_gas_fees, estimate_gas) that also answer gas-pricing questions, leaving the agent to guess which to pick.

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