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

No annotations are provided, so the description carries the full burden, and it discloses valuable operational context beyond the schema: the underlying eth_getStorageAt mechanism and the pricing/payment model ($0.005 per call over x402 in USDC). It still omits edge-case behavior such as what is returned for an empty/unset slot.

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-loaded with the core action and use case, then mechanism, then cost; nothing is redundant. The middle sentence is a sentence fragment ('How you inspect...') that reads slightly awkwardly, but the information density is high.

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 must convey the return shape, and it does so by stating the slot is decoded as hex, integer, and address. For a single-slot read across multiple chains, this is close to complete, though error/empty-slot behavior remains unstated.

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 description coverage is 100%, so the slot, chain, and address parameters are already fully documented in the schema, including the decimal-or-0x-slot-key nuance. The description adds decoding-format detail (hex/integer/address) but nothing about parameter syntax beyond the schema, making the baseline of 3 appropriate.

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: reads a raw storage slot of any contract, with the decoding formats named. It is clearly distinguishable from evm_call, evm_balance, and evm_erc20_balance, which read higher-level state rather than raw slots.

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 a concrete when-to-use case (proxy implementation slots, owners, paused flags with no public getter), which explains why an agent would reach for raw storage instead of a typed read. It does not, however, name a specific alternative sibling or an explicit when-not-to-use condition.

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