browser_localstorage_list

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

No annotations provided, so description carries full burden. It states it lists all pairs for the current origin, implying a safe read operation. However, it does not disclose whether it returns an empty list, performance implications, or any side effects. For a simple list tool, this is minimally adequate but lacks depth.

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, efficiently stating the core function. No wasted words. However, it could be expanded slightly to cover parameters or output without sacrificing conciseness.

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?

Given no output schema and only a brief description, the tool lacks context on return format (e.g., list of objects with key/value), behavior for empty storage, and the role of session_id. The description is too terse for an agent to reliably invoke without additional context.

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 only parameter, session_id, is documented only in the schema with a type and default. The description does not explain its purpose, how it affects the listing, or how to use it. With 0% schema description coverage, the description fails to compensate, leaving the agent uninformed.

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?

Description clearly states the tool lists all localStorage key/value pairs for the current origin. The verb 'List' and resource 'localStorage key/value pairs' are specific, and it distinguishes from siblings like browser_localstorage_get (which likely gets a single key) and browser_localstorage_set.

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 on when to use this tool versus alternatives like browser_localstorage_get or browser_sessionstorage_list. No mention of prerequisites, context, or 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.