Clear the HTTP cache

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

Annotations already flag destructive/mutating behavior, and the description adds useful context: the operation targets the on-disk cache and is a different mechanism from ClearDataService. It stops short of stating irreversibility or whether in-memory cache or active tabs are affected.

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 core action and scoping rules. Dense but every clause carries information; the parenthetical API names are mildly noisy but justify the sibling distinction.

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?

With only two optional params, no output schema, and annotations covering the safety profile, the description supplies nearly everything needed: defaults, per-scope behavior, and sibling routing. Missing only confirmation of what persists after the clear and how it relates to browser_clear_site_cache.

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 baseline is 3, but the description adds real semantics beyond the schema: it explains the domain-vs-origin distinction in prose and, critically, what omitting both parameters does (whole-cache clear). That default behavior is not obvious from the schema alone.

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?

States a specific verb and resource ('Clear the on-disk HTTP cache'), names the underlying API, and explicitly separates itself from browser_clear_data by describing the different service path. An agent can identify exactly what this does without opening the schema.

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?

Gives clear conditional routing: use origin for a single site, domain for a base domain, no args for the whole cache, plus an explicit exclusion against browser_clear_data. The one gap is that browser_clear_site_cache, the semantically closest sibling in the list, is never mentioned or distinguished.

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