browser_manage_storage

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

The annotations already signal destructive behavior (destructiveHint=true), so the description needed to add context beyond that. It does not specify that 'clear' clears all storage (since key is not required for clear), nor does it mention that 'set' overwrites existing values. The description merely restates the action enum from the schema without adding new safety or semantic details.

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, focused sentence that front-loads the core purpose. Every word contributes to meaning, with no filler or redundancy. It is appropriately minimal for the tool's complexity.

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?

The schema and annotations cover parameters and safety, but the description does not clarify edge behaviors such as clearing the entire storage when no key is provided, or what the 'get' action returns. It is adequate for a simple tool but leaves these contextual gaps for the agent to infer.

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%, so the schema fully documents each parameter (action, storageType, key, value). The description adds no additional meaning beyond what the schema provides, so the baseline of 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?

The description clearly states the tool's function: 'Inspects, sets, or clears values in local/session storage.' The verb+resource structure is specific and unambiguous, and it distinguishes this tool from sibling browser tools that handle navigation, clicks, or DOM interaction.

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?

Although no explicit alternatives are mentioned, the description clearly implies usage: it is the only tool for interacting with local/session storage among the siblings. The scope is unambiguous, so an agent can infer when to call it. It lacks explicit 'use this tool when...', but the uniqueness of its resource provides clear context.

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