handle_dialog

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

The description discloses only the basic action of handling a dialog. It omits critical behavioral details such as what happens if no dialog is present, whether the tool waits for a dialog, how dismissal differs from acceptance, or any return values. With no annotations to provide safety or behavioral context, the description fails to convey these important traits.

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 concise sentence that is front-loaded with the main purpose. No word is wasted, but the verb 'handle' could be more precise (e.g., 'accept or dismiss'). Overall, it is appropriately sized and easy to parse.

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 with three simple parameters and no output schema, the description is minimal but still incomplete. It lacks any context about dialog interaction flow, error conditions, or how the tool integrates with page navigation. An agent would have to infer behavior from the parameter names alone, which is inadequate.

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 the baseline is 3. The description does not add any parameter semantics beyond what the schema already explains; the accept/promptText semantics are clearly documented in the schema. The description only adds a generic mention of dialog types, which is redundant.

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 it handles JavaScript dialogs (alert, confirm, prompt), which is a specific resource. Although the verb 'handle' is somewhat generic, the parenthetical list of dialog types makes the purpose unambiguous. It distinguishes from sibling tools by being the only dialog-handling tool.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. Usage is only implied by the dialog types, with no context about dialog blocking, timing, or fallback behavior. This is minimal guidance at best.

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