browser_localstorage_delete

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

The description explicitly states the action is destructive (via annotations destructiveHint: true), and the title repeats the purpose. However, the description itself does not add behavioral context beyond what annotations provide, such as whether the action triggers side effects (e.g., page reload), is reversible, or requires certain permissions. With annotations already covering the destructive nature, the description meets the baseline but adds no extra transparency.

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 is front-loaded and directly states the action. It wastes no words and is efficiently structured. It earns a high score for brevity, though it could be slightly expanded without becoming verbose (e.g., clarifying scope).

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 (1 param, no output schema), the description is minimally sufficient for a basic delete operation. However, it lacks context about what happens if the key does not exist (e.g., error or no-op), whether the action affects other storage types, and the browser state prerequisites (e.g., a page must be loaded). For a destructive action, these gaps reduce completeness.

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 input schema has 1 parameter (key) with 100% description coverage—the schema already describes 'key' as 'Key to delete'. The description does not add additional context about the parameter (e.g., format, length limits, case sensitivity). Since schema coverage is complete, a baseline score of 3 is appropriate; the description provides no extra value for parameter understanding.

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 'Delete a localStorage item' clearly states the verb ('Delete') and resource ('localStorage item'), which aligns with the tool's name. However, it does not differentiate itself from sibling tools like 'browser_localstorage_clear' (which deletes all items) or 'browser_cookie_delete' (which deletes cookies but could be confused if the agent conflates storage types). A minimal distinction is implied by the resource name, but no explicit differentiation is provided.

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 given about when to use this tool versus alternatives. For example, there is no mention that this tool deletes a single item by key, whereas 'browser_localstorage_clear' deletes all items. There is also no context about prerequisites (e.g., needing to navigate to a page first) or when not to use it (e.g., if you need to delete session storage, use session storage tools). The agent must infer usage from the tool name and input schema alone.

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