import_session

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

No annotations are provided, so the description carries the full burden. It discloses that the tool restores cookies and storage and that navigation is required for the import to take effect, which is a key behavioral trait. However, it does not mention potential side effects such as overwriting existing session data or whether the tool requires any prior state, leaving some ambiguity.

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 two sentences with no wasted words. The first sentence front-loads the purpose, and the second provides a crucial usage instruction. It is appropriately sized for the tool's simplicity.

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 simplicity of the tool (two parameters, no output schema, no annotations), the description covers the core behavior and the activation step, making it sufficient for an agent to understand when and how to use it. It does not detail tab targeting or return values, but the schema covers parameter specifics, and the description is adequate for this straightforward operation.

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 provides descriptions for both parameters (sessionData and tabId), achieving 100% coverage. The tool description does not add extra parameter semantics beyond implying that sessionData comes from a prior export, but it does not explain format or specific usage of tabId further.

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 identifies the tool's function as importing previously exported session data to restore cookies and storage, using a specific verb and resource. This distinguishes it from sibling tools like export_session (which exports) and set_cookie (which sets individual cookies).

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 usage after a prior export and explicitly instructs the user to navigate after import to activate the session, providing clear context on when to use the tool. It doesn't explicitly mention alternatives or exclusions, but the sibling context and the restoration purpose make the intended use fairly evident.

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