cookie_export

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

No annotations are provided, so the description must carry the transparency burden. 'Export' implies a non-mutating read, but the description does not explicitly confirm absence of side effects or explain cookie scope/sensitivity beyond the schema. It adds the session-transfer context, but falls short of full behavioral disclosure.

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 short sentences with no filler. Each sentence earns its place: the first defines what the tool returns and the second identifies the primary use case.

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 single-parameter, no-output-schema tool, the description is mostly complete: it defines the return as a JSON string and names the companion import tool. It could add a note on the exact return shape or limitations, but nothing critical is missing.

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 coverage is 100%, with the domain parameter already documented as 'Filter by domain (empty = all)'. The description adds no extra meaning to the parameter, so a baseline 3 is appropriate.

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?

Clearly states the tool exports all cookies as a JSON string, with a specific verb and resource. The phrase 'as JSON string' and the pairing with cookie_import distinguish it from similar siblings like cookie_export_file and cookie_list.

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?

Explicitly says to use it with cookie_import to transfer session, giving a clear intended workflow. Does not state exclusions or compare with cookie_export_file, but the companion-tool guidance is strong.

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