browser_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, and it offers only the bare mutation verb. It does not say whether an existing cookie with the same name is overwritten, whether the cookie is session- or persistent-scoped, whether a page must be loaded, or whether the change is immediately visible to the page.

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 short, front-loaded sentence with no filler, so it is structurally clean. But it is terse to the point of under-specification rather than genuinely concise, since nothing beyond the obvious is conveyed.

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 mutation tool with no annotations, no output schema, and zero parameter documentation, the description is materially incomplete. An agent lacks the origin/scoping, overwrite, and persistence details needed to invoke it confidently.

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% and the description mentions no parameters at all, while the schema has four (name, value, path, domain) with defaults. The agent gets no meaning for path/domain scoping or required name/value pairing from the prose.

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 ('Set a cookie in the browser'), so an agent immediately knows the operation and target. It does not, however, distinguish itself from nearby siblings such as browser_get_cookies or browser_set_headers, leaving the differentiation to naming 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?

There is no guidance on when to set a cookie versus using browser_set_headers, browser_eval, or browser_clear_storage, nor any prerequisites (e.g., whether a page/tab must be active or whether the cookie applies to the current origin). Usage must be fully inferred.

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