browser_clear_storage

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

Lists specific storage types cleared and explains the allOrigins parameter effect. Annotations already indicate destructiveHint=true, but the description adds valuable detail on what exactly gets destroyed without contradiction.

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?

Two sentences, front-loaded with the main action, no unnecessary words. Efficient and clear.

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?

Covers purpose, usage scenario, parameter effect, and a post-action note (reload). No output schema needed; annotations and description together provide full context for this simple tool.

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 already describes the single boolean parameter well. Description adds context about using it to wipe the session, but schema coverage is 100%, so baseline is 3; the extra usage context raises it to 4.

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?

Clearly states the verb 'Clear' and specifies the resources (cookies, localStorage, IndexedDB, cache, service workers) and the scope (current origin or whole session via allOrigins). Distinct from sibling tools like browser_reload or browser_navigate.

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?

Provides explicit use cases: 'log out or test a fresh-user flow' and advises to 'reload afterward'. Does not explicitly mention when not to use, but gives clear context.

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