browser_localstorage_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Delete' clearly implies destructive action, but the description does not mention permanence, what happens if the key does not exist, whether it only affects the current origin, or the return value.

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, front-loaded sentence with no filler. Every word earns its place, clearly conveying the action and the parameter's purpose.

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 destructive tool with no annotations and no output schema, this description is under-specified. It does not disclose side effects, error behavior, or return values, and it lacks guidance distinguishing it from closely related storage deletion tools.

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 0%, so the description must compensate. It mentions 'by key', which maps to the required 'key' parameter, but adds no detail about key format, validity, or behavior for non-existent keys. The schema already names the parameter, so the description adds minimal semantic value.

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 the action 'Delete' with the resource 'localStorage item' and the exact scope 'by key'. This distinguishes it clearly from sibling tools like browser_localstorage_list, browser_localstorage_set, and browser_localstorage_clear.

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 provides no guidance about when to prefer this tool over alternatives such as browser_localstorage_clear for clearing all items or browser_sessionstorage_delete for sessionStorage. The usage context is only implied by the name and basic description, with no exclusions or alternative routing.

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