browser_sessionstorage_get

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

Annotations already declare readOnlyHint true, destructiveHint false, and openWorldHint true, so the basic safety profile is covered. The description adds no new behavioral details (e.g., it doesn't mention that the key must exist or what happens if missing). Bar is lowered due to pre-existing annotations, but no extra value is added.

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, straightforward sentence with clear structure. Front-loaded and directly informative. Still room to add contextual guidance without becoming verbose.

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 a simple tool with one required parameter and clear annotations, the description is adequate for basic usage. However, the lack of output schema or behavioral notes (e.g., return value format, error behavior) leaves mild gaps for an 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?

Schema coverage is 100% and the description of the 'key' parameter in the schema is minimal ('Key to get'). The description adds no semantics beyond what the schema provides, so the baseline 3 is appropriate.

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 clearly states it retrieves a sessionStorage item by key. The verb 'get' and resource 'sessionStorage item' are specific, and the tool is unambiguously distinguished from sibling tools like browser_sessionstorage_set or browser_sessionstorage_delete.

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, it doesn't mention browser_sessionstorage_list for listing all keys, or browser_localstorage_get for local storage. The description offers no context about prerequisites or use cases.

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