send_mouse_click

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

The description adds behavioral detail not present in annotations, namely that the click is a 'press+release', and discloses the run_interactive requirement. However, it does not clarify whether the pointer is moved to the coordinates first or mention potential side effects, which is a minor gap given the annotations provide no safety hints.

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 three sentences, each earning its place: the core action, alternatives, and a prerequisite. No filler or redundancy, and key information is front-loaded in the first sentence.

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 (4 params, 2 required, no output schema), the description covers the essential context: what it does, when to use it, and what is required. Parameter details are handled by the schema, so the description is nearly complete. A minor omission is the lack of clarification about pointer movement behavior.

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%, so the baseline is 3. The description only paraphrases 'coordinates' and does not add extra meaning about the button or doubleClick parameters, which are already well-documented in the schema.

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 'Send a mouse click (press+release) at specific coordinates', specifying the action, target, and scope. It also distinguishes itself from sibling tools by explicitly naming send_mouse_motion and send_mouse_drag, making its 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 explicit guidance: 'For cursor movement, use send_mouse_motion. For dragging, use send_mouse_drag.' It also notes the prerequisite 'Requires run_interactive', giving clear when-to-use and when-not-to-use context with specific alternative tools.

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