browser_sessionstorage_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe, read-only nature is covered. The description adds no further behavioral context (e.g., that it lists all keys, potential performance considerations, or that an empty storage returns an empty list). Without annotations the description would be insufficient, but here it merely restates the function without adding new behavioral insights.

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, front-loaded sentence: 'List all sessionStorage key-value pairs'. Every word is necessary and contributes to clarity. No extraneous information.

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 list tool with no output schema, the description minimally states what it does. However, it omits details about the return format (e.g., array of objects with key/value fields), behavior for empty storage, or potential side effects. Given no output schema, the description should provide a bit more structural context to fully guide the agent.

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 tool has zero parameters, and the schema description coverage is 100% (vacuous). Per rubric, a zero-parameter tool earns a baseline of 4. The description does not add parameter details (as none exist), but does not detract.

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 uses the specific verb 'List' and identifies the exact resource 'all sessionStorage key-value pairs'. This clearly distinguishes the tool from sibling tools like browser_sessionstorage_get (which retrieves specific keys) and browser_localstorage_list (which operates on localStorage).

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 explicit guidance is provided on when to use this tool versus alternatives such as browser_sessionstorage_get or browser_localstorage_list. The usage is implied by the tool name and sibling context, but the description lacks statements like 'Use this to get all sessionStorage entries at once' or 'When you need a specific key, use browser_sessionstorage_get instead.'

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