browser_delete_cookies

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

No annotations provided, so description bears full burden. It only states 'Delete cookies' but does not disclose scope (all cookies?), side effects (e.g., session termination), or whether the operation is reversible. For a destructive tool, this is insufficient.

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 a single sentence, which is concise. However, it lacks critical details that could be added without harming conciseness (e.g., 'all cookies'). It is not overly verbose, but also not optimal.

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?

Given no output schema, the description should indicate return behavior (e.g., success indication). It also fails to clarify if deletion applies to all cookies or a subset. For a simple tool, it is missing essential context.

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?

No parameters exist (0 params), and schema description coverage is 100%. Baseline of 4 is appropriate since there is nothing to add beyond the schema.

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?

Description states 'Delete cookies from the browser' with a clear verb+resource. The plural 'cookies' hints at bulk deletion, distinguishing it from sibling 'browser_delete_cookie' (singular). However, it does not explicitly specify 'all cookies' or allow parameter selection.

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?

No guidance on when to use this tool over alternatives like browser_delete_cookie (singular) or browser_get_cookies. The description fails to mention context such as 'use to clear all cookies' or 'use when you need to remove entire cookie store.'

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