clear_cookies

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is largely covered, and the description usefully adds the "all"/"current context" scope. However it omits that this logs the user out of the context and is not undoable — meaningful caveats given the tool clears state wholesale. The tension with destructiveHint=false is worth noting but cookie clearing is recoverable session state, so it is not a true contradiction.

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?

A single front-loaded sentence with no filler; verb and scope arrive immediately.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Still, for a state-clearing tool the description doesn't say whether it applies across all tabs in the context or whether it requires a loaded page, leaving an agent to guess at invocation conditions.

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 takes zero parameters, so the schema carries no semantic load the description must compensate for; the baseline for a parameterless tool applies. The description does add the one scope qualifier that matters (current context vs all contexts).

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 ("Delete") and resource ("cookies") plus a scope qualifier ("all", "current context"). It implicitly distinguishes itself from get_cookies/set_cookies, but never names those siblings or clarifies the boundary explicitly.

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?

There is no guidance on when to reach for this versus get_cookies/set_cookies, no prerequisite (must a page be loaded in the context?), and no mention of the consequences of wiping all cookies versus selectively removing them.

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