manage_storage

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Access and modify', which does not reveal that delete and clear are destructive operations or that modifying storage can affect the current page's runtime behavior. It does not mention side effects, reversibility, or the scope (current origin).

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 a single sentence, front-loaded with the core function. There is no redundant text, and the message is immediately clear. The emoji '🆕' is minor noise but does not detract significantly.

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?

Despite the schema having good parameter descriptions, the tool description lacks any context about the operational environment (e.g., current page), return values, or error conditions. There is no indication of when to use this tool in a broader browser automation workflow. Given that no output schema exists and annotations are absent, the one-sentence description is insufficient 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 provides descriptions for all 4 parameters (100% coverage), including the action and type enums, so the schema already explains parameter meaning. The description does not add any extra information about parameters, but since coverage is high, the baseline score of 3 is appropriate.

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 identifies the resource (localStorage and sessionStorage) and the general actions (access and modify). It distinguishes itself from sibling tools like manage_cookies since it covers storage, not cookies. However, it could be more explicit about the specific actions (get, set, delete, clear) rather than using the broad 'modify'.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that manage_cookies should be used for cookie operations, nor does it provide context about when storage manipulation is appropriate. The description lacks any usage scenarios or exclusions.

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