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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false; the description usefully reconciles the non-idempotent hint by explaining that every call is charged, so repeats are not free. It also discloses malformed-input handling (400, uncharged) and the fee model, which goes beyond the annotations. However, much of the tail of the description is pricing boilerplate rather than behavioral context about the read itself (e.g. what a zero slot looks like, block-tag semantics).

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, return shape, and the sibling alternative are front-loaded in the first two sentences, which is ideal. The final pricing/credits sentence is dense and partly commercial boilerplate, though cost is genuinely relevant to an agent deciding whether to call repeatedly.

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 carries the return-value burden and does so ('the 32-byte word, as a number and, when it holds one, as an address'). Error behavior, cost, and the proxy alternative are all covered, so an agent has everything needed to invoke it correctly.

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 the baseline is 3, but the description adds real meaning: it clarifies that the slot accepts a decimal index or a 0x 32-byte key and that such keys correspond to mapping and proxy storage slots. It also supplies a concrete address example, which aids format compliance beyond the schema's terse '0x contract address'.

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 ('Read one raw storage slot of a contract on Scroll') and names the underlying RPC (eth_getStorageAt), plus describes the return shape. It is clearly distinguishable from siblings like scroll_call or scroll_proxy.

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?

Explicitly prescribes when to use it ('inspect contract state that has no getter, owners or implementation pointers') and redirects the proxy case to scroll_proxy. This is exactly the when/when-not/alternative structure the dimension rewards.

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