browser_cookie_clear

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

The description adds the scope 'all' beyond the annotation 'Clear cookies' and is consistent with destructiveHint: true. However, it does not disclose additional behavioral traits such as impact on sessions, authentication, or domain scope. With annotations already marking it destructive, the description adds modest value.

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, direct phrase with zero wasted words. It is front-loaded and efficient, earning a top score for conciseness.

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 simple destructive action with no parameters or output schema, the description is adequate but could be improved by clarifying the scope of cookies (e.g., current origin vs. all storage). It provides the core function but leaves ambiguity that may affect correct usage.

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?

The tool has no parameters, and the schema coverage is 100%. Per the baseline rule for 0 parameters, a score of 4 is appropriate. No parameter documentation is needed, and the description correctly omits it.

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 'Clear all cookies' uses a specific verb (clear) and resource (cookies), and clearly distinguishes from sibling tools like browser_cookie_list, browser_cookie_get, browser_cookie_set, and browser_cookie_delete, which have different purposes.

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 (e.g., browser_cookie_delete for specific cookies), nor does it mention contexts where clearing all cookies is inappropriate or requires caution. It is a bare statement with no usage direction.

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