browser_localstorage_clear

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states what gets destroyed ('all localStorage' for the active origin), which is transparent about the destructive scope. However, it does not mention irreversibility, side effects on the active page, or the return value, which would add useful context for a destructive operation.

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, compact sentence that states the action, resource, and scope with no wasted words. It is front-loaded and immediately understandable.

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 zero-parameter tool with no output schema, the description is largely sufficient: it identifies the action, resource, and origin scope. It could improve by noting that the operation is destructive and irreversible, but the core information needed to invoke the tool correctly is present.

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 tool has zero parameters, so the baseline is 4. The description correctly adds no parameter detail because there is none. It appropriately focuses on the operation's scope instead.

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 states a precise operation ('Clear') on a specific resource ('all localStorage') and scopes it to 'the active page's origin'. This clearly differentiates it from sibling tools like browser_localstorage_delete (which removes specific keys) and browser_sessionstorage_clear (different storage area).

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 conveys clear usage context: use this to remove the entire localStorage for the current origin rather than individual keys. It does not explicitly name alternatives or state when not to use it, but the 'all' scope strongly implies bulk clearing versus targeted deletion via browser_localstorage_delete.

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