browser_storage_clear

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

No annotations are provided, so the description carries the full burden. Clearing storage is a destructive, irreversible data-loss operation, yet the description says nothing about which origins are affected, whether the page reloads, whether the session must be active, or whether a session_id mismatch is an error. Only the bare action is conveyed.

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 short sentence with the action front-loaded — efficient, but the terseness is under-specification rather than genuine conciseness for a destructive mutation with two parameters.

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?

An output schema exists, so return values need not be explained. For a destructive, unannotated, 0%-covered two-parameter tool, however, the definition omits scope, side effects, and parameter meaning — not enough for an agent to call it safely.

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 0%, so the description must compensate. It hints at the 'kind' concept ('local/session') but never explains the enum values, the default of 'both', or what the required session_id identifies. Both parameters are effectively undocumented.

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 (clear) and resource (local/session storage), which distinguishes it from siblings like browser_storage_get, browser_storage_set, and browser_cookies_clear. It does not, however, clarify scope (current page origin vs. all origins), so the purpose is clear but not fully bounded.

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 when-to-use guidance, no prerequisites, and no mention of the adjacent alternatives (browser_cookies_clear for cookies, browser_storage_set for writes). The agent must infer that this is the correct tool purely from the name.

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