Set Browser Cookies

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

The description adds behavioral context beyond the annotations: it mentions that successful results echo cookie values for MCP callbacks and verification, and that the batch is bounded. This provides useful insight into return behavior and limitations without contradicting the annotations (readOnlyHint=false, destructiveHint=true).

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 extremely concise, consisting of two short sentences. The first sentence states the core action, and the second adds valuable information about the result. No wasted words.

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?

Although the schema is rich with many cookie fields (name, value, same_site, priority, etc.), the description only covers the batch concept and echo result. It does not explain field semantics, required vs optional fields, or potential side effects. For an agent to invoke correctly, it would need to rely entirely on the schema, which does not provide human-friendly descriptions.

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?

With schema description coverage at 0%, the description completely fails to explain the 'cookies' parameter or its sub-fields. The only hint is 'batch', which merely paraphrases the schema's array type. No additional meaning is provided for any parameter.

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 'Set a bounded batch of browser cookies' with a specific verb and resource, clearly distinguishing it from sibling tools like browser_cookies_get, browser_cookies_delete, and browser_cookies_clear. The action and scope are immediately understandable.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what it does, leaving the agent to infer usage from the name and context.

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