save_login

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

With no annotations, the description fully bears disclosure. It reveals key behaviors: saving cookies and localStorage, closing the visible window, enabling headless authenticated sessions, and the need to re-run interactive_login on expiration. It does not detail failure modes or overwrite behavior, but is sufficiently transparent.

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?

Two sentences with no waste. The first sentence encapsulates the core actions (capture, save, close), and the second provides the outcome and lifecycle. Every sentence earns its place.

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 simple tool with one parameter and no output schema, the description gives a complete picture: what it does, how it affects the session, and the follow-up action. It is thorough enough for an agent to understand the tool's role.

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 covers 100% of the single parameter with a clear description. The tool description reinforces that the project must have an interactive_login in progress, which adds context but does not substantially exceed the schema's information. Baseline 3 with slight added value.

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 captures cookies and localStorage from an in-progress interactive_login, saves it, and closes the window – a specific verb+resource action. It distinguishes from sibling tools like interactive_login (initiates login) and close_session (only closes without saving).

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 says to use it when there is an in-progress interactive_login and mentions re-running interactive_login when the session expires, providing clear usage context. It does not explicitly exclude alternatives, but the sibling set implies close_session for just closing.

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