Get Web Storage

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

Beyond the annotations (readOnlyHint, openWorldHint), the description discloses two key behavioral traits: values are redacted unless include_values is set, and retrieval is bounded (as a map). This adds significant context that annotations do not provide, helping the agent understand defaults and limitations.

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?

The description is a single, concise sentence that front-loads the action ('Read') and presents all key information without redundancy. Every clause adds value.

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?

For a simple read tool with an output schema and clear annotations, the description covers the essential behavior (key vs map, redaction). The context of sibling tools and the schema fill in any remaining gaps, making it complete for an agent to understand and invoke 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 67% (key and include_values have descriptions, area does not). The description adds meaning by explaining 'by key or as a bounded map' (corresponding to key) and 'redacted unless explicitly requested' (corresponding to include_values). It does not mention the area parameter, but the schema's enum provides clear options.

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?

The description clearly states the verb 'Read' and the resource 'localStorage or sessionStorage' with specifics ('by key or as a bounded map, with values redacted unless explicitly requested'). It distinguishes from sibling tools like storage_set and storage_clear by making the read-only nature explicit.

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 clearly implies the tool is for reading web storage, offering both key-based and map-based access. While it does not explicitly mention alternatives or exclusions, the context is sufficient for an agent to infer when to use this tool versus siblings like storage_set or storage_clear.

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