browser_sessionstorage_list

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

With no annotations, the description itself carries the behavioral burden, and it does state the core behavior: a non-mutating listing operation restricted to the active origin. It does not disclose edge cases such as empty storage behavior or exact return formatting, but for a simple read-only storage listing these are minor gaps.

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 nine words states the resource, action, and scope with no filler, repetition, or buried details. Every element earns its place.

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 zero-parameter read with no output schema, the description is essentially complete: it names what is listed, which storage area, and the origin scope. It could add a sentence about return format, but 'key-value pairs' already implies the output shape.

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, so the description is not required to add parameter-level detail; the baseline for a no-parameter tool is 4. The existing description contributes no parameter semantics, but none are 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 uses the specific verb 'List' with the resource 'sessionStorage key-value pairs' and scopes it to 'the active page's origin', making the operation unambiguous. It is clearly differentiated from sibling tools such as browser_sessionstorage_get (single-key retrieval), browser_sessionstorage_clear (removal), and browser_localstorage_list (a different storage area).

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 provides no guidance about when to choose this tool over alternatives or when not to use it. It does not mention sibling tools like browser_sessionstorage_get or browser_localstorage_list, so an agent must infer the intended use solely from the tool name and the generic action.

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