browser_sessionstorage_set

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

The description does not add behavioral context beyond what annotations already provide. Annotations indicate readOnlyHint=false, openWorldHint=true, destructiveHint=true, which imply mutation and potential side effects. However, the description says nothing about what 'setting an item' entails (e.g., does it overwrite existing keys? Does it require a page to be loaded?). Without elaboration, the agent lacks critical behavioral understanding.

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 extremely short (4 words) and front-loaded, which meets conciseness. However, it fails to provide necessary context, making it under-specified rather than effectively concise. The length is minimal, but the content is insufficient for a valuable description.

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 lack of output schema and low sibling differentiation, the description is incomplete. It does not explain what happens after setting (e.g., confirmation, persistence, or side effects on the page). For a mutation tool with destructiveHint=true and no output schema, more details are needed to ensure safe usage.

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 2 parameters with 100% description coverage, so the schema already describes 'Key to set' and 'Value to set'. The description 'Set a sessionStorage item' adds no further meaning beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 'Set a sessionStorage item' clearly states the action (set) and the resource (sessionStorage item). However, it does not distinguish itself from sibling tools like browser_sessionstorage_set and browser_cookie_set, all of which set storage items. The verbosity is minimal, leaving ambiguity about what 'sessionStorage' is in context.

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. For example, there is no mention that this tool is for browser session storage (not cookies or localStorage) or that it requires a page context. The description is too vague to help an AI agent decide when to invoke it.

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