firefox_mouse_click

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

Without annotations, the description carries full burden but only says 'Click', offering no details on side effects such as page navigation, state changes, mouse movement, or wait behavior. The 'observe' parameter hints at post-click snapshotting but is not explained.

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 single-sentence description is extremely concise, which is positive, but it omits many necessary details, making it insufficient rather than efficiently complete. It front-loads the core action but sacrifices depth.

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 8 parameters, no output schema, and no annotations, the description is far from complete. It does not explain return values, error handling, or parameter interactions (e.g., how coordinates and selector relate). Significant gaps remain.

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 38%, and the description adds little beyond schema: 'x', 'y' lack coordinate system context; 'selector' mentions 'fire-fodex element ref' (typographical issue); 'observe' enum values are unexplained. The description fails to compensate for low schema coverage.

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 'Click by viewport coordinates or selector/ref' clearly states the action (click) and two primary methods (coordinates or selector/ref), distinguishing it from sibling tools like firefox_mouse_move. However, it does not clarify the distinction from firefox_click or what 'ref' refers to.

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 vs. alternatives like firefox_click or firefox_mouse_move, nor are prerequisites (e.g., sessionTabId) or context (e.g., coordination with other actions) mentioned. The agent is left guessing about appropriate invocation scenarios.

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