browser_localstorage_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral info beyond confirming it lists all pairs. However, for a simple read-only tool, the description is sufficient; no further behavioral detail (e.g., potential size limits, encoding) is necessary given the annotations. No contradiction detected.

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, clear sentence that conveys the full purpose without any wasted words. It is front-loaded and efficient, earning its place perfectly.

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 parameterless, read-only tool with no output schema, the description is close to complete. It could optionally mention the return format (e.g., 'returns a list of key-value pairs'), but the absence is minor given the tool's simplicity and the existing annotations.

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% with zero parameters, so the baseline is 4 per guidance. The description adds no parameter details (none needed) but effectively communicates the tool's scope (all pairs), which aligns with the empty schema.

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 'List all localStorage key-value pairs' clearly states the specific verb (list), resource (localStorage key-value pairs), and scope (all). It distinguishes itself from siblings like browser_localstorage_get (which retrieves a specific key) and browser_localstorage_clear (which deletes all entries), though it doesn't explicitly call out these differences.

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 description implies usage for listing all localStorage entries but provides no explicit guidance on when to use this tool vs alternatives like browser_localstorage_get for specific keys or browser_storage_state for a full storage snapshot. No context on prerequisites or temporal conditions (e.g., page must be loaded) is given.

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