1s_storage_read

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

No annotations are provided, so the description must disclose behavior. It correctly notes the slot format constraint and the underlying method, but it does not explicitly state that it is a read-only operation or describe any side effects. While the read-only nature is implied, a clearer statement would help.

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 concise sentences with no superfluous words. The description is front-loaded with the core purpose and supported by usage guidance in the second sentence.

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?

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description covers the essential aspects. However, it omits details about the return format (a 32-byte hex string) and the default network, which would enhance completeness for an agent.

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%, but the description adds value by reinforcing that the slot must be a 32-byte hex-encoded value, which is more specific than the schema's generic 'hex-encoded' description. This helps ensure correct parameter usage.

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?

Description clearly states the tool reads a raw storage slot via eth_getStorageAt, providing a specific verb and resource. It effectively distinguishes from siblings like 1s_contract_code and 1s_simulate_call.

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 advises using this tool for low-level state inspection with examples (proxy implementation slots, packed storage). However, it does not explicitly state when not to use it or compare to alternatives, which would further aid selection.

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