pikvm_shortcut

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

No annotations are provided, so the description carries full burden. It mentions that keys are pressed simultaneously, but does not describe key release behavior (e.g., hold vs. press-release), error handling, or whether it is a read-only or write operation. The example provides some context but lacks depth.

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 extremely concise: one sentence followed by an example. Every part is informative and front-loaded. There is no unnecessary text.

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 tool with one parameter and no output schema, the description is mostly complete. It could mention valid key code formats or that it is a write operation, but the given information is sufficient for basic usage. With no annotations, a bit more context would be ideal.

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 coverage is 100% as the parameter 'keys' has a description. The tool description adds an example (Ctrl+Alt+Delete) but does not provide additional meaning beyond the schema. The schema already explains the parameter, so the description adds minimal value.

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 sends a keyboard shortcut with multiple keys pressed simultaneously, using a specific verb and resource. It distinguishes itself from sibling tools like pikvm_key (single key) and pikvm_type (typing text) by emphasizing the simultaneous press aspect.

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 an example but does not explicitly state when to use this tool versus alternatives like pikvm_key or skill_send_shortcut. The usage is implied from the name and description, but no when-not-to-use or alternative guidance is given.

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