vnc_set_clipboard

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

With no annotations, the description carries the full burden of behavioral disclosure. It only restates the tool's function ('Set the remote clipboard') and provides no details about side effects, overwriting behavior, requirements, or error conditions. The agent receives no transparency beyond the basic action.

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 short sentence with no filler, but it is under-specified rather than efficiently complete. It earns a moderate score for brevity but loses points because it lacks critical context that a fuller description would provide.

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?

The tool has a simple schema (one string parameter) and no output schema or annotations, so the description must provide the context. It gives the core action and resource, but omits any mention of prerequisites, return values, or behavior in edge cases, making it incomplete for an agent to use confidently.

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 description does not elaborate on the required 'text' parameter at all. Schema description coverage is 0%, so the description must compensate, but it fails to explain what 'text' represents, any constraints, or how it is used. The parameter name alone is insufficient.

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 'Set the remote clipboard' clearly specifies the action (set) and resource (remote clipboard), distinguishing it from sibling vnc_get_clipboard which retrieves the clipboard. It is unambiguous and directly states what the tool does.

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 usage guidance is provided. The description does not mention when to use this tool, any prerequisites (e.g., an active VNC connection), or alternatives such as vnc_get_clipboard. Usage is only inferred from the name and description.

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