Browser Storage

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

No annotations are provided, so the description carries the full behavioral burden. It never discloses that 'set'/'clear' are mutating (and that 'clear' wipes data), what permissions or loaded-page state are required, or what 'get' returns for a missing key. Only the abstract rationale (skip login flows) is added.

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, zero filler, with the core action/resource statement front-loaded before the integration guidance. Nothing needs trimming.

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?

With six parameters, no annotations, and no output schema, the description should do more: it doesn't explain what 'get' returns, what 'clear' affects by default, or how mode/sessionId interact with execution. The identity and one integration path are covered, but an agent lacks enough to call it confidently in edge cases.

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% with enums on action/area/mode, so the schema already documents key, value, area, mode, action, and sessionId. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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 concrete verbs (get/set/clear) against a specific resource (localStorage/sessionStorage on the current page), and explicitly distinguishes itself from browser_cookies as the companion tool for full session state. An agent can identify what it does and where it sits relative to siblings without opening the schema.

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?

Gives a clear use case: persist/restore auth tokens and app state to skip repeated logins, and names the co-used sibling browser_cookies. It does not state when NOT to use it (e.g., per-call ephemeral state vs. durable storage) or offer an alternative for simple cookie reads.

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