browser_handle_dialog

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

No annotations are provided, so the description carries the full behavioral burden. It hints at one-shot scoping via 'next' but says nothing about the default handling if this is never called, whether the call is blocking, or what happens to the dialog's return value. Substantial behavioral gaps remain.

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 tight sentence with no filler, and the scope constraint ('next') is front-loaded. It is not bloated, but it is under-specified rather than genuinely concise for a four-parameter configuration tool.

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?

An output schema exists, so return values need not be explained. But with no annotations, 0% parameter documentation, and an ambiguous 'handled', the agent lacks what it needs to invoke this correctly — notably how to choose between accepting and dismissing.

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 description coverage is 0% for all four parameters (once, accept, session_id, prompt_text), and the description mentions none of them. The meaning of 'accept' vs 'once' vs 'prompt_text' — the entire point of the tool — is left completely undocumented.

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 names a specific resource (the next JavaScript dialog) and an action (set how it should be handled), so the agent knows this is a dialog-policy tool and it is unique among the siblings. However, 'handled' is vague — it never says accept/dismiss/prompt-text, which is the actual semantic content of the tool.

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?

There is no when-to-use guidance: it does not say whether this must be called before a dialog appears, what happens if a dialog is already blocking, or how it relates to browser_click/browser_evaluate which trigger dialogs. The word 'next' implies one-shot scope but nothing more.

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