browser_sessionstorage_set

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not mention that setting an item overwrites an existing key, that sessionStorage is per-tab/origin, or any error conditions. The only added behavioral context is 'active page's origin', which is minimal.

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 concise sentence that states the action and scope with no unnecessary words. It is well-structured and front-loaded.

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 tool with two string parameters and no output schema, the description still falls short: it omits parameter semantics and usage alternatives. Without annotations or schema descriptions, the agent is left without enough information to call the tool confidently.

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% and the description does not explain what 'key' and 'value' mean, how they should be formatted, or any constraints. With zero parameter documentation in both the schema and description, the agent cannot properly understand the inputs.

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 a specific verb and resource ('Set a sessionStorage item') and adds the scope ('on the active page's origin'), making the core purpose clear. However, it does not differentiate among the many storage siblings (localStorage, cookies), so it lacks explicit sibling differentiation.

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 given on when to use this tool versus alternatives like browser_localstorage_set, browser_cookie_set, or browser_storage_save. The description only states the action without any context or exclusions, leaving the agent to infer the appropriate choice from the name alone.

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