load_session

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this mutates state without being destructive; the description's mention of cookies and localStorage is consistent with that. It doesn't disclose whether existing cookies/storage are overwritten, whether the browser must be at a matching origin, or what happens on a name miss – relevant context for a state-mutating tool.

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 front-loaded sentence that identifies the action, payload, and target, with no filler.

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?

An output schema exists, so return values need not be explained, and the core action is clear. However, for a state-mutating restore tool the description leaves the 'name' selector undocumented and omits overwrite behavior, which an agent needs to call it correctly.

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 schema documents nothing about the single 'name' parameter, and the description never mentions it at all – no indication that it selects which saved session to restore or that it defaults to 'default'. This is the main gap in the definition.

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?

States a specific verb (restore) and resources (cookies and localStorage) with a clear scope (current browser), and anchors itself to the sibling save_session, so an agent can distinguish it from set_cookies or get_cookies without opening the schema.

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 pairing with save_session makes the usage condition clear (rehydrate a previously saved session), but it never states prerequisites such as an already-open browser or what to do if no saved session exists, and it doesn't contrast with set_cookies as an alternative.

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