vnc_connect

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

With no annotations, the description must carry behavioral context but only says 'Connect'. It doesn't disclose that this likely establishes the primary session for other tools, whether it supports SSH tunneling, or what happens if already connected. The minimal wording leaves the side effects unclear.

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, concise sentence with no wasted words. It's front-loaded with the essential action, though it lacks structure or supporting details; still, it is appropriately brief for such a minimal statement.

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?

This tool has nested parameters (ssh object), no output schema, and no annotations, yet the description only provides the basic purpose. It lacks crucial context like connection prerequisites, whether it blocks, return format, or relationship to other VNC tools, making it inadequate for reliable use.

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 adds no parameter information. Host, port, password, and the nested ssh object are entirely unexplained, leaving the agent to guess their meaning and usage.

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's function: 'Connect to a VNC server' – a specific verb and resource. It distinguishes itself from sibling tools like vnc_screenshot or vnc_mouse_move by focusing on establishing the connection.

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 relative to alternatives, such as using it before other VNC tools or disconnecting with vnc_disconnect. No exclusions or prerequisites are mentioned.

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