browser_storage

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

With no annotations, the description carries the full burden of disclosing behavior, but it only says 'Manage' which implies both read and write operations without any detail. It does not state side effects, persistence semantics, permission needs, or whether actions are destructive. The minimal description fails to communicate any meaningful behavioral traits.

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 concise sentence with no wasted words, which is structurally clean and front-loaded with the resource. However, it is so brief that it borders on under-specification, yet that is a completeness issue rather than a conciseness issue. It earns points for being tight and direct.

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?

For a tool with 5 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain what actions are available, how key/value/session parameters interact, and what the expected outcomes are. An agent cannot reliably call this tool correctly based on the description and schema alone.

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 coverage is 100%, so each parameter has a description, but those descriptions are simply the property names restated (e.g., 'Storage key') without conveying expected values or formats. The tool description itself adds no parameter semantics. Since the schema descriptions are uninformative, the baseline of 3 is applicable due to coverage but no extra value is provided.

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 states a clear resource (localStorage/sessionStorage) and a verb (Manage), but 'Manage' is vague and doesn't specify the exact operations (e.g., get, set, delete) or scope. It distinguishes from siblings like browser_cookie by pointing to web storage, but lacks the specificity needed to select it confidently over other storage-related tools.

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 conditions like choosing between localStorage and sessionStorage, or when to prefer this over cookie-related tools. The agent is left to infer usage from the name and schema.

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