Clear all localStorage entries in the current page context to remove stored data and prevent stale state. Pass the session ID from browser_navigate.
Delete every localStorage entry in the current page context.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | Session ID returned by browser_navigate |
Changes observed during successful MCP inspections.
v2.15.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully confirms the operation is a total wipe ('every entry') limited to the current page context rather than all tabs, but adds nothing about reversibility, permissions, or whether other origin storage is affected.
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?
A single, front-loaded sentence with zero redundancy, sized correctly for a one-parameter destructive utility.
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 destructive utility with complete schema coverage, no output schema, and annotations carrying the safety burden, the definition is essentially sufficient. Only the absence of any usage context keeps it short of full marks.
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% for the single session_id parameter, and the schema already documents it as the ID returned by browser_navigate. The description adds no additional parameter meaning, so the baseline 3 applies.
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 (Delete) and resource (every localStorage entry) scoped to the current page context. An agent can immediately distinguish it from siblings like browser_clear_cookies, browser_set_local_storage, and browser_get_local_storage without opening a schema.
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 gives no when-to-use guidance, no alternatives, and no conditions under which the destructive wipe should be preferred over targeted removal via browser_set_local_storage. Usage is only inferable from the tool name, which is weaker than explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.