clear_cookies

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. 'Clear all cookies' communicates a destructive operation but does not disclose that it may log the user out, that the effect is irreversible, or that it only affects cookies and not local/session storage. The description adds little beyond what the tool name already implies.

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 a single clear sentence. It is appropriately sized for such a simple tool, though it is nearly a restatement of the tool name and provides no additional structural detail.

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 zero-parameter utility, the description is minimally adequate, but it omits important context for an AI agent, such as the scope of 'all cookies' and the impact on the current browsing session. Given the destructive nature of clearing cookies and the existence of related storage tools, a bit more context would make the tool safer and easier to invoke correctly.

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 zero parameters, so there is no parameter information to clarify. The baseline score of 4 applies because no parameter semantics are needed; the description adequately addresses the action for a parameterless tool.

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 ('Clear') and resource ('all cookies'), clearly distinguishing it from sibling tools like get_all_cookies, save_cookies, and load_cookies. However, it does not clarify whether 'all cookies' means all cookies in the browser context or only cookies for the current domain, leaving some ambiguity.

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 is provided about when to use this tool versus alternatives such as save_cookies, load_cookies, or get_all_cookies. The description simply states the action without suggesting use cases, prerequisites, or situations where clearing cookies might be undesirable.

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