browser_get_storage

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

No annotations exist, so the description carries the full burden. 'Read' implies a safe non-mutating operation, but it says nothing about the return shape (key/value map vs raw strings), behavior on empty storage, cross-origin restrictions, or whether values are JSON-serialized. For a zero-annotation tool this leaves real behavioral questions unanswered.

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?

One sentence, front-loaded with the verb and resource, no filler. It is arguably too terse rather than padded, so the sizing issue is under-specification, not verbosity.

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?

Low-complexity tool with a fully documented single param, so little is required. However, with no output schema the agent has no idea what the read returns, and the description does nothing to close that gap.

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% and the single param is a fully documented enum with a stated default, so the schema does the work. The description's 'and/or' loosely echoes the 'both' option but adds no syntax or format detail beyond the schema. 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?

Specific verb (Read) plus the exact resource (localStorage and/or sessionStorage) and scope (active tab). An agent can distinguish it from browser_get_cookies or browser_get_html without opening a schema, though it never names those siblings as alternatives.

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 phrase 'of the active tab' implies the precondition (tab must be active/selected) and 'and/or' hints both stores can be merged, but there is no explicit when-to-use versus execute_script or browser_get_cookies, and no stated prerequisites such as page load state.

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