vnc_mouse_move

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

With no annotations provided, the description carries full responsibility for disclosing behavior, but it reveals nothing beyond the tool's name. There is no mention of coordinate system (e.g., screen vs window), movement speed, whether the pointer moves instantly or smoothly, or any side effects.

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 short sentence, which is under-specification rather than effective conciseness. It is brief but at the expense of all useful information, so it does not earn credit for efficiency.

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 tool with two required parameters and no annotations or output schema, the description is completely inadequate. It fails to explain coordinate semantics, usage context, or how it differs from sibling mouse tools, making it impossible for an agent to use correctly without additional knowledge.

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 defines x and y as numbers but provides no descriptions, and schema description coverage is 0%. The description adds no meaning about what these coordinates represent, their units, or their bounds, failing to compensate for the schema's lack of detail.

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 'Move the mouse' merely restates the tool name without specifying the target coordinate system, context, or distinction from similar tools like vnc_mouse_drag or vnc_mouse_click. It states the verb and resource but offers no meaningful elaboration, making it a tautology.

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?

There is no guidance on when to use this tool versus alternatives such as vnc_mouse_drag or vnc_mouse_click. The description provides no context, prerequisites, or exclusions, leaving the agent without any decision support.

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