pikvm_mouse_click

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states that the tool optionally moves before clicking, but omits details like button hold behavior, error handling, required permissions, or what happens if coordinates are invalid. The minimal info is insufficient for safe usage.

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, front-loaded 14-word sentence that conveys the core function without any superfluous words. Every part is necessary and immediately useful.

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?

Although the tool is simple, the description lacks completeness. It does not mention return values (no output schema), error conditions, or prerequisites like calibration. For a physical action tool, more context about behavior and constraints is needed to ensure correct invocation.

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 has 100% coverage of parameters with descriptions. The description adds marginal value by noting 'Optionally move to a pixel position first' for x/y, but does not enrich button or state beyond the schema. Given high schema coverage, a baseline of 3 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 clicks a mouse button on a remote machine, with optional movement to a pixel position. This verb+resource structure is specific and distinguishes it from siblings like pikvm_mouse_move (only move) and pikvm_mouse_scroll (scroll).

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios like needing a simple click vs move operation, nor does it reference siblings or specify prerequisites (e.g., calibration). This leaves the agent with insufficient context for tool selection.

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