browser_localstorage_clear

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

The description discloses that the operation is scoped to the current origin, which is beyond the name. However, without annotations, it lacks details on irreversibility, impact on other storage types, permission requirements, or synchronous behavior. It meets minimal expectations but does not fully compensate for the absence of annotations.

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 very concise (one sentence), containing no superfluous words. It could be improved by including parameter information, but as a standalone statement it is efficiently structured.

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, the description captures the core behavior (clear all localStorage for current origin) and there is an output schema presumably covering return values. However, the lack of parameter explanation and usage context leaves gaps for a complete understanding.

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 one optional parameter (session_id) with no description in the schema, and the tool description does not explain its purpose or effect. With 0% schema description coverage, the description should compensate but fails to add any meaning to the parameter.

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 action ('clear') and the resource ('all localStorage for the current origin'), leaving no ambiguity about what the tool does. It distinguishes from siblings like browser_cookie_clear or browser_sessionstorage_clear by the specific resource mentioned.

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 provides no guidance on when to use this tool versus alternatives such as browser_localstorage_remove (to remove specific items) or browser_cookie_clear. The agent is not informed about prerequisites or context for invoking this tool.

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