Import cookies via the Local API

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description aligns with a write operation. It adds behavioral context by specifying the write target ('on-disk data directory') and the dependency on the 'running desktop app'. It also implies that this method bypasses cloud sync, which is valuable. However, it does not detail potential side effects or failure modes, but the annotation coverage reduces that burden.

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 concise sentences. The first sentence states the core action, and the second provides guidance. No redundant or filler content. It is front-loaded and every word 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?

The description covers the main purpose and usage guidance, and the annotations provide safety-related context. However, with no output schema and low schema coverage, the description leaves gaps around parameter details and potential failure modes. It is adequate but not complete for an agent to fully understand the tool's behavior without further inference.

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 only 25%, with only domain and expirationDate described. The tool description does not elaborate on parameters like profileId, cookies structure, cloudSyncDisabled, or browserProfilePassword. While the mention of 'cloud sync disabled' hints at cloudSyncDisabled, it does not explain the parameter semantics. The description adds little beyond the 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 clearly states the action: 'Write cookies into a profile's on-disk data directory through the running desktop app.' The verb is specific, the resource is identified, and the method distinguishes it from the sibling import_cookies tool. The title also emphasizes 'Local API', reinforcing the distinction.

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 provides explicit guidance: 'Prefer import_cookies unless the profile has cloud sync disabled.' This tells the agent when to choose this tool over the sibling, and also implies the prerequisite that the desktop app must be running. This is direct and actionable.

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