browser_manage_storage

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

With no annotations, the description must disclose behavioral traits. It covers basic functionality but omits details like domain scope for cookies, that clearing localStorage affects the current origin, and that 'set' requires both key and value (implied but not explicit). The description lacks some context for safe 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?

Two sentences with no wasted words. The first sentence defines functionality, the second provides usage context. Information is front-loaded and easy to parse.

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?

The tool has 5 parameters and no output schema. The description covers the core actions but lacks details on return values, domain behavior, and precondition requirements. Given sibling tools and the complexity, it is adequate but not fully complete.

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%, so baseline is 3. The description restates the storage types and actions but adds no new parameter details beyond the schema. It does not explain conditional requirements (e.g., domain for cookies) or output format.

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 verbs (get, set, clear) and resource (browser storage: localStorage, sessionStorage, cookies). It distinguishes from sibling tools by specifying storage manipulation, which is unique among the browser tools listed.

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 explicit use cases: 'testing auth flows, clearing state between test runs, or inspecting cached data.' This guides the agent on when to use the tool, though it does not contrast with alternatives or state when not to use it.

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