browser_handle_dialog

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

The description adds no behavioral detail beyond the annotations. Annotations already flag destructiveHint=true and readOnlyHint=false, but the description does not explain what 'handling' entails, potential side effects, or requirements like promptText. It neither contradicts nor enriches the annotations.

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 vague phrase that under-specifies the tool. It is not a case of efficient brevity but rather a failure to convey necessary information; every word merely repeats the name.

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 tool that handles browser dialogs, the description omits crucial context such as when a dialog appears, what happens when accept is true or false, and how promptText is used. The schema covers parameter names but not the overall usage context, leaving the agent under-informed.

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% for both parameters ('accept' and 'promptText'), so the schema carries full parameter semantics. The description adds nothing, but with complete schema coverage, a baseline of 3 is appropriate.

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' simply restates the tool name and title, providing no specific verb or resource scope. It does not indicate whether the tool accepts, dismisses, or otherwise interacts with the dialog, nor does it distinguish it from sibling 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?

There is no guidance on when to use this tool relative to alternatives, such as when a JavaScript dialog blocks navigation or when to supply promptText. The description offers no context, exclusion criteria, or alternative tool suggestions.

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