browser_handle_dialog

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

No annotations are present, so the description carries the full burden. It discloses that the tool can mutate state via 'accept/dismiss' but does not mention side effects, whether a dialog must exist, or behavior when no dialogs are pending. This is a significant gap for a mutating tool.

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, efficient sentence that front-loads the primary actions. There is zero fluff, and every word contributes to the meaning.

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?

With 6 parameters, no output schema, and no annotations, the description is under-specified. It does not explain the listing output format, how to handle prompt dialogs with promptText, or what happens with multiple dialogs. This is insufficient for a tool of this complexity.

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 covers only 33% of parameters (pageId and sessionId have descriptions). The description implies that id, accept, dismiss, and promptText relate to dialog actions, but it doesn't explicitly map them. Parameter names are self-explanatory to some degree, but the description should compensate more for the missing schema descriptions.

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 clearly states the tool's dual purpose: 'List pending dialogs or accept/dismiss one dialog.' The verb 'List' and action phrase 'accept/dismiss' with the resource 'dialog' are specific and distinct from sibling tools, which focus on navigation, clicking, and other browser actions.

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 explicit when-to-use or alternative guidance is provided. However, the tool is uniquely named for dialog handling among the siblings, so its usage is implied. The description lacks context on when to list versus accept/dismiss, or prerequisites like existing dialogs.

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