browser_sessionstorage_clear

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

The annotations include destructiveHint: true, which already indicate the tool is destructive. The description reinforces this by stating it clears all sessionStorage, aligning with the annotation. It adds clarity beyond annotations by specifying the scope ('all sessionStorage' rather than a key), but does not detail irreversible effects or impact on page state, which is acceptable given the annotation already flags destruction.

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 of only three words, which perfectly captures the action with no extraneous information. It is front-loaded and efficient, well-suited for a straightforward zero-parameter tool.

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 has no parameters, no output schema, and annotations cover destructiveness, the description is complete enough. It succinctly states the action and scope. No further details about return values or side effects are necessary for such a simple operation.

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?

There are zero parameters, and the schema coverage is 100%. The description is minimal but sufficient since there is nothing to document beyond the action. The clarity that it clears all sessionStorage (without filters) is helpful but inherent in the tool's design.

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 verb 'Clear' and the resource 'sessionStorage', which is a specific browser storage area. It distinguishes this from siblings like browser_sessionstorage_list, browser_sessionstorage_get, browser_sessionstorage_set, and browser_sessionstorage_delete, as well as browser_localstorage_clear, by targeting a different storage scope.

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 is provided on when to use this tool versus alternatives such as browser_sessionstorage_delete for targeted removal or browser_localstorage_clear for local storage. There is no mention of prerequisites or context, such as needing a page with sessionStorage or handling potential data loss.

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