browser_handle_dialog

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it never says that accepting a dialog commits the action (possibly a destructive confirm), that declining dismisses it, or how prompt input is supplied. With no annotations-vs-text conflict, this is a gap rather than a contradiction.

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?

Three words are not concision but under-specification, matching the low-calibration pattern. There is nothing to front-load because there is essentially no content.

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 mutating, open-world tool with a required boolean that determines whether a page action is committed or cancelled, the description leaves the essential decision logic unexplained. The session isolation and promptText behavior must be inferred entirely from the schema.

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 100%, so the schema already explains accept, session, and promptText; the baseline of 3 applies. The description contributes no additional semantics, such as what happens if promptText is omitted for a prompt dialog.

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?

"Handle a dialog" is nearly a restatement of the tool name and title. It does identify the resource (a browser dialog) but gives no indication of what handling entails — accepting, dismissing, or supplying prompt text — so an agent cannot distinguish it from siblings like browser_click or browser_press_key without opening the schema.

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 guidance on when a dialog exists or when to call this tool. It does not mention that dialogs block other page actions, nor how to discover a pending dialog (e.g., via browser_snapshot or browser_wait_for), and it names no alternatives.

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