browser_handle_dialog

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds no behavioral details. It does not explain the side effects of accepting vs. dismissing, the role of promptText, or how the tool interacts with the browser state. Annotations carry the burden, but the description contributes nothing.

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 only four words, which is under-specified rather than concise. It lacks front-loaded structure and does not earn its place because it adds no value beyond the tool name. A useful description would at minimum clarify the dialog type and action.

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 moderate complexity (2 parameters, no output schema, no param enums), the description is far from complete. It omits return value, behavioral nuances, and usage context. Even a simple tool requires explaining what 'handle' means. The description leaves critical gaps.

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 coverage is 100%, so the input schema already documents both parameters clearly. The description adds no additional semantic context (e.g., when promptText is needed, what 'accept' does). Baseline of 3 is appropriate since the schema does the heavy lifting.

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 essentially a tautology of the tool name and annotation title. It does not specify the type of dialog (alert, confirm, prompt) or what 'handling' entails (accepting, dismissing), making it vague and indistinguishable from a generic label.

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 any of the 23 sibling tools (e.g., browser_click, browser_type). It fails to mention prerequisites (e.g., a dialog must exist) or contexts where alternative tools would be more appropriate.

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