sessionstorage_get

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

No annotations are provided, so the description carries the full burden. It communicates a read operation through the verb 'Get', but it does not describe the return format, behavior for a missing key, or whether sessionStorage is read in its entirety when no key is given. Basic read behavior is implied, but key edge-case behavior remains undisclosed.

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 sentence with no filler, front-loading the operation and resource. Every word contributes meaning, and it is appropriately brief for a simple getter tool.

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 one-optional-parameter getter with no output schema, the description covers the core invocation paths: all data or a specific key. It is complete enough for an agent to select and call the tool, though mentioning behavior for a nonexistent key would have made it fully airtight.

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 schema provides only an optional string property with no description, so the description adds the critical meaning: omitting the key retrieves all sessionStorage data, while providing a key retrieves that specific value. This directly compensates for the 0% schema description coverage.

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 the operation (Get) and the resource (sessionStorage data), and distinguishes it from sessionstorage_set and sessionstorage_clear by using the verb 'Get'. It does not explicitly differentiate from localstorage_get beyond the storage type, so it stops short of perfect sibling differentiation.

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 tool is for retrieving sessionStorage data, but it provides no explicit guidance about when to use this tool versus alternatives like localstorage_get, and gives no exclusions or prerequisites. Usage context is only implicit in the verb and noun.

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