save_session_state

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

With no annotations, the description carries the full burden. It discloses what is captured and that it is in-memory, but omits details on whether it overwrites existing snapshots, return values, or side effects. Adequate but lacks depth.

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 wasted words, achieving conciseness. However, it sacrifices essential parameter explanation, so it loses a point for not being structured to include key details.

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?

Given the complexity of capturing storage across multiple realms and one required parameter, the description is incomplete. It fails to explain the parameter's purpose and does not provide enough behavior context to confidently use the tool alongside many similar siblings.

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 has 0% description coverage for the required 'name' parameter. The description does not explain what 'name' is for, its format, or its role. This is a critical gap that significantly hinders correct tool invocation.

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 tool takes a snapshot of cookies, localStorage, and sessionStorage from all known window realms into an in-memory snapshot. It uses a specific verb and resource, and the scope differentiates it from siblings like dump_session_state or restore_session_state.

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 explicit guidance on when to use this tool versus alternatives like dump_session_state or save to file. The description does not mention prerequisites, exclusions, or typical use cases, which is problematic given the many similar sibling tools.

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