browser_handle_dialog

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

With no annotations, the description carries full burden. It explains the accept/dismiss behavior via the accept boolean and mentions prompt_text for filling prompts before accepting. It also notes that dialogs remain open until handled, which is key behavioral info.

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 extremely concise with two sentences, no fluff, and front-loads the core action. Every sentence adds value.

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 simple dialog handling tool, the description covers most aspects: purpose, main behavior, and two of three parameters. Missing session_id explanation is a minor gap. Output schema exists, so return value details are not required.

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 description must compensate. It explains accept (accept or dismiss) and prompt_text (fill prompt before accepting), but does not explain session_id, leaving a gap. Two of three parameters are covered.

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's purpose: accepting or dismissing JS dialogs (alert/confirm/prompt). It specifically identifies the action and resource, distinguishing it from sibling tools which cover other browser interactions.

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 to use it (when a dialog is open) and notes that dialogs stay open until handled, but does not explicitly state when not to use it or mention alternatives. No sibling tool addresses dialogs, so context is clear.

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