browser_handle_dialog

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description contributes no additional behavioral context. It does not explain side effects (e.g., what happens when accepting vs. dismissing, whether it unblocks the page, or the impact of promptText). The description merely repeats the concept of 'handling' without disclosing consequences.

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 concise in word count (one short sentence) but is under-specified. It earns no place because it adds no information beyond the tool name. True conciseness requires conveying necessary details efficiently; this fails by not conveying anything useful.

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?

The description omits critical context: it does not mention that this applies to JavaScript dialogs, that a dialog may block further browser actions, or that it requires user interaction via accept/promptText. With no output schema, the description should clarify success/failure conditions, but it does not. It is insufficient for an agent to understand the full scope of the tool.

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 parameters are already well-documented: 'accept' and 'promptText' have clear descriptions. The tool description adds no extra meaning beyond the schema, which meets the baseline for high coverage. No enhancement needed.

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 direct restatement of the tool name 'browser_handle_dialog', providing no specifics about what 'handle' means (accept/dismiss). It fails to distinguish from sibling tools like browser_handle_download or browser_dismiss_dialog (if it existed). The verb 'handle' is vague and the resource 'dialog' is only slightly more specific than the name.

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?

No guidance is given on when to use this tool, such as 'Use when a JavaScript dialog (alert/confirm/prompt) appears' or 'Only needed when a dialog blocks interaction'. There is no mention of alternatives or prerequisites. The description simply states the action without contextual triggers.

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