browser_cookies_set

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says cookies go into the current context. It omits whether existing cookies are overwritten or merged, whether the write is ephemeral or persisted, what permissions or an active session are required, and any error behavior for invalid domains.

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?

It is a single front-loaded sentence with no filler, which is structurally clean, but the brevity stems from under-specification rather than disciplined editing. Space freed by the short sentence is not used to clarify any parameter or behavior.

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?

An output schema exists so return values need not be explained, but this is a mutation tool with no annotations and zero parameter documentation. For a tool whose correctness depends on cookie object shape and session scoping, the description leaves too much unstated.

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 0% across three parameters. The description names "cookies" only implicitly, and the shape of each cookie object (name/value/domain/path/expiry) and the purpose of fallback_domain are entirely undocumented in both schema and description, so callers cannot construct a correct call.

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?

States a concrete verb and resource ("Set cookies") plus the target scope ("current browser context"), so an agent knows this writes cookies into the live session. It does not, however, distinguish itself from siblings like browser_cookies_save or browser_storage_set, which a reader must infer from the names alone.

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 offers no when-to-use guidance, no prerequisites, and no comparison to browser_cookies_get, browser_cookies_save, or browser_cookies_clear. The agent must guess whether this is the right tool versus sibling cookies tools.

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