Clear cookies

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

The description goes beyond the destructiveHint and idempotentHint annotations by explaining the scope (browser-wide, not per site/tab), the lack of undo, and the fact that localStorage is untouched. This gives the agent critical context about side effects and limitations.

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?

Three short, focused paragraphs. The first sentence states the action, the second clarifies scope and consequences, and the third provides use cases and a caveat. Every sentence earns its place; no redundancy.

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 no-parameter tool, the description covers all essential aspects: what it does, scope, irreversibility, recovery path, and edge case (localStorage). With an output schema present and no parameters, this is fully complete.

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 the schema fully covers parameter semantics. The description adds behavioral context rather than parameter details, which is appropriate. The baseline of 4 applies here.

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 clearly states 'Delete every cookie in the browser' with a specific verb and resource. It distinguishes itself from per-site or per-tab tools and from related siblings like get_cookies or set_cookie by emphasizing the browser-wide scope.

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?

Explicitly names use cases: testing first-time-visitor flow or resetting consent banner decisions. Also provides an alternative for recovery via load_session, guiding the agent when to use this tool versus when to use a session restoration tool.

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