save_session_from_browser

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

No annotations are provided, so the description carries full burden. It explains the tool connects via CDP, saves all aa.com cookies, and depends on an external browser session. Does not specify overwrite behavior, but overall 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?

Description is well-structured: one-liner purpose, numbered workflow, then parameter docs. Every sentence adds value, no fluff, front-loaded.

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 tool's complexity (requires prior steps, state-changing), the description covers prerequisites, workflow, and parameters. There is an output schema, so return value need not be explained. Could mention multiple runs, but overall complete.

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 has 0% description coverage. The description adds value by explaining each parameter's purpose (account name, port) and details why port should be passed as string, with defaults clearly stated.

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?

Description clearly states the tool pulls cookies from a Chromium browser started by aa-auth-browser and saves them. It includes a workflow that differentiates it from sibling tools (e.g., check_auth_status are read-only queries).

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?

Explicit workflow steps are provided: run aa-auth-browser, log in, then call this tool. While no direct alternatives are mentioned, the context makes usage clear. Lacks explicit when-not-to-use, but strong for its purpose.

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