browser_sessionstorage_delete

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

Annotations already declare destructiveHint=true, so the agent knows this is a destructive operation. The description adds no detail beyond that, such as whether deletion is permanent, if it triggers events, or if it requires the page to be open. The description does not contradict annotations, but adds minimal 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 sentence, very concise, and front-loaded with the action. No extra words, but it could be slightly more informative without being verbose.

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 the tool is simple (1 required param, no output schema, no nested objects), the description is mostly adequate. However, it lacks context about the scope (e.g., current browser tab's sessionStorage) and expected behavior if the key is missing or storage is empty. This is a minor gap for a simple tool.

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%, with the 'key' parameter described as 'Key to delete'. The description does not add extra meaning beyond what the schema provides, such as whether the key is case-sensitive, URL-encoded, or if wildcards are supported. Baseline 3 is appropriate as schema already covers the parameter.

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 'Delete a sessionStorage item' states a clear verb-action (delete) and resource (sessionStorage item). It distinguishes from siblings like browser_sessionstorage_get, browser_sessionstorage_set, and browser_sessionstorage_clear by specifying deletion of a single item, not retrieval, setting, or clearing all.

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 when-to-use or when-not-to-use guidance is provided. It does not mention that this is for browser-based sessionStorage only, when to prefer this over browser_sessionstorage_clear, or that the key must exist. No alternatives or exclusions are stated.

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