vnc_mouse_drag

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

With no annotations provided, the description bears full responsibility for disclosing behavior, but it simply says 'Perform a drag and drop' without explaining the mechanics (e.g., button press, movement, release). It fails to inform the agent about timing, coordinates handling, or potential 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 extremely concise, consisting of a single sentence. While there is zero waste, it is under-specified and lacks essential detail, making it merely short rather than appropriately concise for a tool with this complexity.

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 has 5 parameters, no annotations, and no output schema, the description is grossly incomplete. It does not explain return values, prerequisites, coordinate system, or any behavioral context, making it inadequate for 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?

Schema description coverage is 0%, and the description mentions none of the parameters (startX, startY, endX, endY, button). It adds no meaning beyond the raw schema, leaving the agent without clues about what values to provide or their significance.

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 'Perform a drag and drop' clearly identifies the action as a mouse drag-and-drop operation, distinguishing it from sibling tools like vnc_mouse_move and vnc_mouse_click. While it is somewhat generic, it is specific enough to convey the core purpose.

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_click or vnc_mouse_move. The description provides no context about drag-and-drop scenarios, leaving the agent to infer usage solely from the tool name.

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