browser_click

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

With no annotations, the description carries full burden. It reveals the Bezier curve movement detail, which is useful, but lacks other behavioral traits like viewport coordinate system assumptions, prerequisites (element visibility), or side effects. The description is informative but incomplete.

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 sentence that efficiently communicates the core action and its method (Bezier curve). No unnecessary words.

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 many sibling tools, the description should clarify when to use this tool versus other click/hover tools. It also lacks details about prerequisites, error handling, and output. The sparse description is insufficient for an agent to fully understand the tool's context.

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 has 0% description coverage, so the description must compensate. It says 'physical coordinates' but does not define the coordinate frame (viewport, screen, document), units, or valid range. This leaves ambiguity about how x and y are interpreted.

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 moves the mouse to physical coordinates via Bezier curve and simulates a left-click. It distinguishes from siblings like browser_double_click, browser_right_click, and browser_hover by specifying left-click and Bezier movement.

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 implies usage for single left-click actions, but provides no explicit guidance on when to use this tool versus alternatives (e.g., double-click, right-click, hover). Given the many sibling tools, more specific usage context would be helpful.

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