firefox_dialog

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

No annotations are present, so the description carries the burden. It mentions that the dialog is blocking the page and can be cleared, but does not detail side effects such as navigation consequences after accepting or dismissing, or behavior when no dialog exists.

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 concise, using two sentences to convey purpose and platform-specific context. No redundant or irrelevant information is included.

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?

The description is adequate for an agent to understand when the tool applies (blocking native dialogs in Firefox). Given there is no output schema and the tool's scope is narrow, the provided context is mostly sufficient, though a note about required action (accept vs dismiss) being mandatory would improve completeness.

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 input schema covers all three parameters with descriptions, giving 100% coverage. However, the descriptions are minimal (e.g., 'Default accept' for action) and do not add deeper meaning beyond the schema itself. The description text adds no additional parameter context.

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 action (accept or dismiss) and the target (native dialog such as alert, confirm, prompt, beforeunload). It also distinguishes the Firefox-specific behavior from Chrome, making the purpose unambiguous.

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 context about Firefox-only behavior but does not explicitly state when to use this tool versus alternatives like javascript_tool or navigate. No clear conditions or scenarios are given for choosing this tool over others.

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