browser_clear_browsing_data

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

No annotations are provided, so the description carries the full burden. It usefully discloses the destructive scope by enumerating exactly what can be wiped (cache, cookies, history, localStorage, passwords, downloads) and the since_ms time filter. However, it never states that the action is irreversible, whether it affects other open tabs/sessions, or what permissions are needed.

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?

Front-loaded with the core action in the first sentence, then concise per-parameter notes. The docstring-style 'Args:' formatting is slightly mechanical but wastes no words and stays small.

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 destructive, no-annotation, no-output-schema tool, the description covers inputs well but leaves notable gaps: it does not warn about permanence, cross-tab scope, or return value. An agent has enough to call it, but not enough to call it safely.

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 0%, so the description must compensate, and it does: it enumerates the valid type values, states the default (all), and explains since_ms as an epoch-ms lower bound. This adds real meaning beyond the bare 'Types'/'Since Ms' schema titles, though it omits whether types accepts a single string vs array.

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?

Clear specific verb+resource: 'Clear browsing data of the given types.' An agent immediately understands the operation. It does not differentiate from near-siblings like browser_cache, browser_cookies, or browser_storage, which conceptually overlap with the clearable types enumerated here.

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?

The description implies when the tool applies (clearing browsing data) and notes that types defaults to all, but offers no guidance on alternatives such as browser_cache or browser_cookies for narrower operations, and no when-not-to-use or prerequisite conditions.

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