cookie_export_file

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the output is all cookies in Playwright format, but it does not state whether an existing file is overwritten, whether cookies are removed from the session, or what path/permission requirements apply. These are moderate gaps, though not fatal for a straightforward file export.

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?

One sentence with no filler: it front-loads the action, scope, destination, and format. The parenthetical about Playwright format adds essential information without bloating the text.

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 single-required-parameter tool with full schema coverage, the description plus schema is enough to invoke the tool correctly and understand the result: what it does, where it writes, and the file format. The lack of an output schema and overwrite/return behavior notes are minor for correct invocation.

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 description coverage is 100% and the only parameter is already described as 'Output JSON file path'. The description adds no additional parameter-level meaning beyond the Playwright format context, so it stays at the baseline for a fully documented schema.

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 states a specific verb and resource ('Export all cookies'), a destination ('JSON file'), and a format ('Playwright format'). This clearly differentiates it from the sibling cookie_export tool, which would otherwise be the main source of confusion.

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 file destination implies this tool should be used when cookies need to be persisted to disk, but the description does not explicitly say when to prefer it over cookie_export or how it relates to cookie_import_file. The usage context is inferable rather than directly stated.

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