browser_handle_dialog

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

Annotations declare destructiveHint=true and readOnlyHint=false, indicating the tool mutates state. However, the description adds no behavioral context beyond these annotations. It does not disclose that accepting a dialog may close it, that dismissing requires setting accept=false, or that promptText is only applicable for prompt dialogs. The description carries no added value.

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 a single sentence, but it is too concise to be useful. It is a tautology that does not front-load actionable information. Every word should earn its place; here, the description fails to inform the agent about what the tool does or how to use it.

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 complexity (handling browser dialogs) and the absence of an output schema, the description is incomplete. It does not explain the return value, the typical sequence (e.g., dialog must be present), or the relationship with other tools like browser_click or browser_navigate. The annotations provide some hints, but the description should carry more of the burden.

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 input schema has 100% description coverage, with clear descriptions for both parameters. The description 'Handle a dialog' adds no additional meaning about the parameters. It does not clarify that 'accept' is required, or that 'promptText' is only relevant for prompt dialogs, which would help an agent understand parameter usage beyond the schema.

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 'Handle a dialog' is a tautology of the tool name 'browser_handle_dialog'. It restates the name without specifying what kind of dialog (e.g., alert, confirm, prompt) or what actions are involved (accept, dismiss, provide text). This fails to distinguish the tool from the many sibling browser tools.

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 no guidance on when to use this tool versus alternatives. It does not mention that this tool is typically used after a dialog appears, nor does it explain that it is needed to proceed with further browser interactions. No exclusions or alternatives are given.

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