Clear Web Storage

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

The description matches the destructive hint annotation and clarifies the storage types (local/session). However, it does not add significant behavioral context beyond the annotation, such as irreversibility or cross-tab effects.

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. Every word contributes to clarity without any redundancy.

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 and the presence of an output schema, the description adequately covers the primary behavior (clear one key or all) and storage context. No additional details are necessary for correct invocation.

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?

The description adds context that key is optional and that clearing can be for local or session storage, but the schema already covers the key parameter's behavior. The area parameter is self-explanatory via its enum, so the description adds minimal extra meaning beyond the schema.

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 that the tool clears one key or all items from localStorage/sessionStorage, with a specific verb and resource. It effectively distinguishes from sibling tools like storage_get and storage_set by focusing on deletion.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., storage_set with empty value) or when not to use it. The context of siblings is broad but not addressed.

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