sessionstorage_clear

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a destructive action ('clear') but does not warn about data loss, irreversibility, or potential impact on other tabs/windows of the same origin. The description lacks transparency beyond the basic operation.

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?

A single sentence of 10 words that efficiently communicates the action, scope, and sibling relationship. No unnecessary words or repetition.

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 simple 'clear' operation with zero parameters and an output schema (implied), the description provides sufficient context: what it does (clear sessionStorage), scope (current origin), and relation to sibling. It does not explain return values but that is likely covered by the output schema. A more complete description might mention that this affects the current session only, but it's adequate.

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?

The input schema has zero parameters, and schema description coverage is 100% (no params to describe). The description does not explicitly state 'takes no arguments', but baseline for 0-param tools is 4. It adds no parameter info, but none is needed.

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 'Clear all sessionStorage for current origin', providing a specific verb and resource. It distinguishes from the sibling tool 'localstorage_clear' by mentioning parity, making its purpose and scope unambiguous.

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 includes 'parity with localstorage_clear', which implicitly guides the agent to use this tool when sessionStorage needs clearing and to consider the sibling for localStorage. While it does not explicitly state when not to use, it implies the complementary relationship.

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