browser_accept_dialog

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

The description accurately indicates that the tool performs a mutation (accepting a dialog) which aligns with the annotation readOnlyHint=false. It explains the behavior (clicking OK) and the types of dialogs handled, though it does not detail error cases (e.g., no dialog present).

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 two sentences long, front-loads the action and resource, and every sentence serves a purpose: defining the action and giving usage context. No wasted 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?

Given the tool's simplicity (no parameters, single action), the description covers all necessary context: what it does, when to use it, and what kind of dialogs it applies to. An output schema exists to handle return values, so further detail is not needed.

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 and the input schema is empty. The description adds value by explaining what action the tool performs (accepting dialogs) and the specific types of JavaScript dialogs it handles.

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 action 'Accept (click OK on) a JavaScript dialog' and lists the dialog types (alert, confirm, prompt). It distinctly differentiates from sibling tool browser_dismiss_dialog, which handles dismissing (cancelling) the dialog.

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 provides a clear usage scenario: 'Call this when a browser action triggers a dialog that blocks further interaction.' It implies when not to use by contrasting with the sibling browser_dismiss_dialog, but does not explicitly state exclusions.

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