vnc_key_tap

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

The word 'tap' implies a press-and-release action, and the 'C-c' example indicates support for key combinations. However, it does not disclose error handling, connection requirements, or whether modifiers are processed natively.

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 one short sentence and includes illustrative examples. It is well-structured and free of redundant information.

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 simple one-parameter tool, the description is adequate but minimal. It lacks any mention of usage context or edge cases, but the low complexity and clear examples keep it from being incomplete.

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 schema only defines a 'key' string with no description. The description adds examples ('Enter', 'C-c') that inform the expected format, which partially compensates for the 0% schema coverage.

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 uses a specific verb 'tap' and identifies the resource (key), with examples ('Enter', 'C-c') that clarify the scope. This distinguishes it from sibling tools like vnc_type_string or mouse click actions.

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 provided on when to use this tool instead of alternatives such as vnc_type_string or vnc_mouse_click. The description simply states what it does without context or exclusions.

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