mouse_click

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

With no annotations provided, the description carries the transparency burden. It reveals the 'glide-free' behavior and supports for right/double click, but it does not clarify whether the cursor physically moves to the target coordinates or remains at its original position, leaving a behavioral ambiguity.

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 two concise sentences, front-loaded with the core action ('Click'), and contains no unnecessary words. It efficiently communicates the tool's capabilities.

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 simple tool with four optional parameters and no output schema, the description covers the primary invocation modes (current position, x/y) and modifiers (right/double). It omits minor details like default left-click behavior, but the schema already labels x/y as screen coordinates, making the description sufficiently complete.

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 100% since all parameters (x, y, right, double) have descriptions. The description adds no additional meaning beyond the schema—it merely restates that clicks can happen at x/y coordinates. Baseline score is appropriate.

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's function with the verb 'Click' and specifies two modes: current cursor position or x/y coordinates. It also mentions support for right and double click, distinguishing it from sibling tools like mouse_drag and mouse_move.

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 when to use the tool (clicking at a location) but does not explicitly contrast it with alternatives like mouse_drag or mouse_move, nor does it provide exclusions or prerequisites. The context is clear but the guidance is not explicit.

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