Set cookie

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

No annotations are provided, so the description carries the full disclosure burden. It conveys mutation ('create or update') and profile scope, but says nothing about whether an existing cookie is overwritten, persistence/session lifetime, required permissions, or domain/path inheritance behavior for a 9-parameter mutation tool.

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?

A single 12-word sentence with the action front-loaded and no filler. It is appropriately sized for the tool, though very lean given the parameter surface.

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 9-parameter mutation tool with no annotations and no output schema, the description is minimal. It omits the url-vs-domain interactions, secure/httpOnly/sameSite implications, and whether the cookie is immediately active in the current session, leaving meaningful gaps an agent would have to guess at.

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%, so every parameter is already documented in the schema (url derives domain/path, path default '/', expirationDate as Unix seconds, etc.). The description adds no parameter detail beyond that, matching the baseline 3.

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 clear verb+resource ('Create or update a cookie') and scopes it to 'the current profile,' which is specific enough to distinguish it from read siblings like browser_get_cookies. It stops short of explicitly naming or contrasting with those siblings, so it doesn't reach the 5 tier.

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?

There is no when-to-use or when-not-to-use guidance. It never mentions browser_get_cookies for reading, nor does it note any prerequisite such as needing a page/tab context before setting a cookie. Usage must be inferred entirely from the verb.

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