browser_handle_dialog

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

The description does not disclose any side effects, such as whether accepting or dismissing a dialog affects the page state. Annotations indicate destructiveHint=true, but the description adds no detail about what 'handle' entails (e.g., whether it blocks or closes). No contradiction with annotations though.

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 single sentence is concise in length but fails to earn its place as it adds no value beyond the tool name. It is structurally minimal to the point of being redundant, providing no new information.

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 is severely incomplete for a tool that interacts with browser dialogs. It does not explain what happens when called, what the return value is (though no output schema), or how it fits into a larger workflow. Lacks essential context for correct usage.

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 schema provides descriptions for both parameters (accept and promptText), so coverage is 100%. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 that restates the tool name without specifying what handling means, what type of dialog, or the expected behavior. It does not distinguish this tool from siblings like browser_click or browser_snapshot.

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 to use this tool versus alternatives, no mention of prerequisites (e.g., a dialog must be present), and no indication of when not to use it. The description provides no operational context.

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