browser_clear_cache

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

With no annotations provided, the description carries the full burden. It discloses the exact data cleared for each scope, notes that 'all' wipes profile-wide HTTP cache and all cookies, and mentions time-bounding. It doesn't explicitly state destructiveness, but the actions imply it. This is strong transparency for a state-clearing tool.

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?

The description is efficient and well-structured, leading with the purpose and then explaining scope logic and defaults. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.

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?

The tool's complexity is moderate due to scope-dependent behavior and session-type variations. The description covers the key decision points (scope selection, defaults) and notes time-bounding. It omits details like error handling or cross-tab effects, but these are minor given the tool's straightforward purpose. Overall, it provides sufficient context for correct invocation.

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 'scope' parameter is thoroughly explained in the description, adding meaning beyond the schema's bare enum and default. However, 'sessionId' is not described in either the schema or the description, leaving its purpose and format ambiguous. With 50% schema coverage, the description compensates for scope but not sessionId.

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 the tool clears browsing state, specifies exactly what is cleared (cookies, storage, cache, service workers) and distinguishes between the two scopes. It is specific, actionable, and differentiates from siblings like browser_hard_reload.

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?

It explicitly states when to use the tool ('before a run that must start clean') and provides detailed guidance on choosing between 'origin' and 'all' based on session type (fresh vs attach). It also clarifies default behavior, which is critical for correct usage.

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