List sessionStorage

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

The description states the action is to 'list' entries, consistent with the readOnlyHint annotation. It also discloses the scope ('current origin'), which is a meaningful behavioral detail. No destructive behavior is implied or contradicted.

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 with no redundant words. It front-loads the action and resource, making it immediately understandable without extra fluff.

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?

The description is complete for a simple read operation. It does not describe the output format, but given the tool's purpose (listing key-value pairs) and the absence of an output schema, the omission is acceptable. The 'current origin' qualifier adds necessary context.

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?

There are no parameters in the input schema, and the description adds no parameter-specific details. Following the baseline for zero parameters, the score is 4 as the description correctly implies no arguments 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' and clearly identifies the resource as 'sessionStorage key-value pairs' scoped to 'the current origin'. This unambiguously distinguishes it from related tools like browser_sessionstorage_get (single key) and browser_localstorage_list (different storage).

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 implies the use case of retrieving all session storage entries for the current page, and the 'current origin' qualifier sets expectations. It does not explicitly contrast with localStorage or mention when to prefer this tool, but for a zero-parameter read operation the guidance is sufficient.

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