browser_errors_clear

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

With no annotations, the description carries full burden. It discloses the destructive action (clearing logs) and the creation of a checkpoint, though it does not detail side effects like impact on previous checkpoints or browser state beyond errors.

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 sentence that concisely conveys the action and purpose, with no extraneous words.

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 zero-argument tool, the description is complete enough to understand the action and its purpose. Minor omission: the checkpoint's role in subsequent validation steps could be elaborated, but not essential.

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 has no parameters (baseline 4). The schema is empty, and the description does not add parameter information, which is appropriate.

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 it clears browser error logs (Console/PageError/Network) and creates a verification checkpoint, distinguishing it from sibling tools like browser_errors (reads errors) and browser_errors_aggregate (aggregates errors).

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 phrase 'to isolate this round of verification errors' implies usage after a validation run to reset error state, providing context. No explicit when-not-to-use or alternatives are mentioned, but the sibling list offers differentiation.

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