browser_dialog

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the write-capable nature is covered structurally. The description usefully adds that dialogs are never auto-accepted (so the agent must handle them explicitly), but it does not explain what accept vs dismiss does to the underlying page or how promptText applies.

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?

Two tight sentences, front-loaded with the resource and scope. No filler, though the second sentence is a caveat rather than a usage instruction.

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 2-parameter tool with an undocumented enum and no output schema, the description leaves real gaps: it never maps the action values to behavior or explains promptText, so an agent must infer the accept/dismiss/prompt semantics from the schema alone.

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% with 2 parameters, and the description explains neither 'action' (whose enum values status/accept/dismiss map directly onto the stated capabilities) nor 'promptText' (presumably the text submitted on accept of a prompt). Only the verbs 'inspect'/'answer' loosely hint at the action values.

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?

States a specific verb+resource: inspect or answer a JavaScript dialog, scoped to the Playwright browser. It reasonably distinguishes it from the sibling chrome_dialog, though it never names that sibling explicitly.

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?

Usage is only implied — the tool is obviously for when a dialog is blocking the browser, but the description gives no guidance on when to use status vs accept vs dismiss, nor any prerequisite or alternative routing.

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