alert

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

With no annotations, the description carries full burden. It merely says 'handle' without disclosing that actions like accept/dismiss are destructive or that send_text requires a text parameter. The schema provides the actions, but the description adds no behavioral context.

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 very short (6 words) but under-specified. While conciseness is good, it sacrifices essential detail; it could be equally concise while including the available actions.

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 complexity (multiple actions, conditional parameter), the description is incomplete. It does not mention that get_text retrieves dialog text, nor does it provide any return value information (no output schema).

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 0%, yet the description does not mention any parameters. It fails to explain the required 'action' parameter with its enum values or the optional 'text' parameter needed for send_text, leaving the agent without guidance.

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 identifies the tool as handling browser alert, confirm, or prompt dialogs, which distinguishes it from sibling tools like click or navigate. However, it could specify the exact actions (get text, accept, dismiss, send text) for greater clarity.

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 guidance is provided on when to use this tool versus alternatives like execute_script or find_element. The description lacks context about prerequisites or scenarios best suited for this tool.

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