safari_set_session_storage

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

The description implies a write operation, which is sufficient given the lack of annotations. However, it does not disclose that values are overwritten on existing keys or that storage is session-scoped. No annotation contradiction.

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, well-structured sentence with no redundancy. It is front-loaded and efficiently conveys the core action.

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?

As a simple setter with no output schema, the description lacks context about return value (likely void), error handling, and the ephemeral nature of session storage. It is not comprehensive for an agent needing full behavioral 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?

Schema coverage is 100% with descriptions for both parameters ('Storage key', 'Value to store'). The description adds no meaning beyond the schema, earning the baseline score.

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 'Set' and the resource 'sessionStorage', directly conveying the tool's function. It distinguishes itself from sibling tools like safari_session_storage (read) and safari_delete_session_storage (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 like safari_set_local_storage or safari_session_storage. The description does not mention session scope or contrast with related tools.

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