session_restore

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

With no annotations, the description carries the full transparency burden. It explains what is restored and where, but does not disclose the most important behavioral trait: whether existing cookies/storage in the target session are overwritten, merged, or rejected, nor what happens if no saved state exists for the given name.

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 and front-loads the primary verb and object. It is concise, though the brevity is a contributing factor to some missing behavioral/parameter detail.

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 state-mutating tool with no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks the overwrite/merge semantics, error behavior for missing saved states, and any indication of what the restore call returns or whether it is destructive.

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 0%, so the description must compensate. It partially does by tying the operation to session_save ('previously saved') and referring to the target as 'active (or given) session', but it never explicitly maps `name` to the saved-state identifier or `sessionId` to the target session.

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 names a specific action ('Restore'), a specific resource set (cookies + localStorage/sessionStorage), and a defined source/target (saved via session_save into active or given session). This clearly distinguishes it from the sibling session_save tool.

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?

States that it must be used with data 'previously saved with session_save' and may target the active or a given session, giving clear selection context. It does not explicitly list exclusion cases or alternative tools, so it stops short of a 5.

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