vnc_type_multiline

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

With no annotations provided, the description carries the behavioral transparency burden. It does state the core behavior ('type multiple lines of text, separated by newlines'), but it does not disclose details such as whether each line is terminated with Enter, whether trailing newlines are sent, or how the input is delivered. The behavior is sufficiently clear for a simple typing tool but not deeply transparent.

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, front-loaded sentence with no filler. Every word adds meaning: it specifies the action, the target, and the line-separator behavior.

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 one required parameter, full schema coverage, and no output schema, the description provides enough context to call the tool correctly. It could mention usage tradeoffs with vnc_type_text, but the low complexity and clear parameter semantics make the current description largely complete.

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 already documents the single parameter as an array of lines with 100% coverage. The description adds useful meaning by explaining that lines are separated by newlines when typed, which is not explicit in the schema. This goes beyond the baseline 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 and resource: it types multiple lines of text separated by newlines. This clearly distinguishes it from sibling tools like vnc_type_text, vnc_click, and vnc_key_press by describing its unique input behavior.

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 implies when to use the tool—when multiple lines of text need to be typed—but it does not explicitly name alternatives or state when not to use it. No explicit guidance is given about choosing vnc_type_text for single-line input, leaving selection partly to inference.

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