get_session_storage_item

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly implies a read operation with no side effects, but it does not disclose behavior when the key is missing, whether the value is returned as a string, or whether the sessionStorage is scoped to the current page/tab. These gaps are notable but the core read-only behavior is evident.

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, focused sentence with no filler. It front-loads the operation and the target storage, making it easy to parse quickly.

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 tool with no output schema and no annotations, the description provides the essential operation but omits important context like return value on missing key, type of the returned value, and any storage isolation caveats. It is minimally viable but leaves an agent uncertain about edge-case behavior.

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 description coverage is 0%, so the description must compensate for the undocumented 'key' parameter. It does not explain what the key represents, accepted formats, or behavior for invalid keys. The description only mentions 'a value from sessionStorage', leaving the parameter semantics entirely to the agent's inference.

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 a specific verb ('Get') and identifies a distinct resource ('value from the page's sessionStorage'). This clearly separates it from sibling tools like get_local_storage_item and set_session_storage_item by naming the exact storage mechanism.

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 gives no guidance on when to use this tool versus alternatives such as get_local_storage_item or set_session_storage_item. There is no mention of prerequisites, exclusions, or context that would help an agent decide between storage access tools.

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