vnc_click

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Click at specified coordinates' and does not reveal whether the pointer is moved to the coordinates first, what coordinate system is used, whether there are side effects, or what happens on failure. This is a minimal mutation-like action with no safety profile or behavioral nuance disclosed.

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 sentence with no filler words, making it maximally concise and front-loaded. Every component of the description earns its place by stating the essential action.

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?

Despite full schema coverage, the tool has no annotations and no output schema. The description does not explain the actual behavioral effect—whether the click happens at the current cursor position or after moving to (x, y)—nor the coordinate system, which is essential for an agent to invoke the tool correctly. For a remote-desktop clicking tool, this is a meaningful gap.

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 100%, so the schema already documents all four parameters. The description adds no extra meaning beyond the schema, but the parameter names are self-explanatory and the baseline score 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 a specific action ('Click') and resource ('specified coordinates'), making the tool's purpose immediately obvious. It also naturally differentiates from sibling tools like vnc_move_mouse, vnc_key_press, and vnc_screenshot because 'click' is distinct and 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?

No guidance is given about when to use this tool versus its siblings or when not to use it. The description does not mention prerequisites, context, or alternative routing, so the agent must infer usage purely from the tool name and generic action.

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