Clear stored data for one site

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

Annotations already declare destructiveHint=true, so the safety profile is covered; the description adds real value by specifying the exact data categories destroyed (cookies, storage, caches) and the deliberate single-site scoping. It stops short of stating irreversibility, whether open tabs need reloading, or container/context interaction.

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 sentences, front-loaded with the verb and the scope constraint, then the safety rationale. The design-rationale clause is slightly chatty but earns its place by deterring accidental global deletion.

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?

A destructive tool with annotations, fully documented params, and no output schema needs scope, destruction set, and safety framing — all present. Missing: whether the call is irreversible, and its effect on a currently loaded page versus persisted profile data.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a constraint absent from the schema: one of host or origin must be supplied. Note this conflicts with the schema's required: 0, leaving ambiguity about enforcement.

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?

Specific verb+resource ("Delete stored data") with an explicit scope qualifier ("ONE host or origin") and an enumeration of what is removed (cookies, storage, caches). It does not, however, distinguish itself from near-identical siblings such as browser_clear_site_cache or browser_delete_cookies, so the agent must infer the difference.

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 'clear everything' path here on purpose" is a useful when-not signal, but it never names the alternative (browser_clear_cache) or the narrower cookie-only sibling. Usage context is implied rather than routed.

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