get_session_storage

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a read operation and the special behavior when key is omitted, which is valuable context beyond the tool name. It does not mention what happens when a key is absent or the exact return format, but it covers the main decision-relevant behaviors.

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 with no filler, front-loading the core action and then adding the optional behavior. Every word 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 simple getter with one optional parameter and no output schema, the description explains the essential behavior and the no-key case. It is slightly thin on return-format details, but the tool is simple enough that this is a minor gap rather than a blocking omission.

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 already documents the key parameter and says 'omit for all', giving this a baseline of 3. The description adds meaning by specifying the outcome difference: getting a value versus returning all keys, which clarifies the parameter's behavioral effect.

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 verb (get), the resource (sessionStorage), and the key behavior: returning a single value or all keys when no key is provided. This differentiates it from sibling storage tools like get_local_storage and set_session_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 tool is for reading from sessionStorage and that omitting the key returns all keys, but it does not explicitly state when to prefer this over alternatives or mention any exclusions. The resource name makes the context clear, but no explicit routing guidance is provided.

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