Delete cookies

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

Annotations declare destructiveHint=true, and the description earns credit beyond them by spelling out exactly what gets destroyed: with no filter it clears every cookie the session can see. That is the single most important behavioral fact for this tool and it is stated plainly.

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?

Two sentences, front-loaded with the action and its filter semantics, ending on the destructive default. No filler and no repetition of schema content.

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 two-optional-param mutation with no output schema and full annotation coverage, the description supplies the action, the filter model, and the destructive default. Nothing an agent needs to call it safely is missing.

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 coverage is 100% and documents both optional params, so the baseline is 3. The description adds real meaning on top: the params are combinable filters and the zero-param case has a distinct, dangerous semantic (delete all) that the schema's empty required list alone would not convey.

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 specific verb + resource ("Delete cookies") plus the underlying BiDi call (storage.deleteCookies), and the filter scoping immediately separates it from browser_get_cookies, browser_set_cookie, and bulk browser_clear_data. An agent can identify the operation without opening the schema.

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?

Gives explicit operational guidance: supply name and/or domain, and only omit both if you intend to wipe every visible cookie. The when-not condition is stated as a warning rather than an alternative-tool routing (e.g. vs browser_clear_site_cache), so it stops just short of a 5.

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