skill_send_shortcut

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

Annotations indicate readOnlyHint=true and idempotentHint=true, suggesting a safe, read-only operation. However, the description implies sending keyboard shortcuts, which typically modify state. This contradiction undermines transparency. Additionally, no behaviors beyond annotations are disclosed.

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 short (6 words), which is concise but insufficient. It is front-loaded but lacks essential information, reducing its value.

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?

Given the absence of parameters and output schema, the description must compensate by explaining purpose, usage, and behavior. It fails to do so, leaving the tool's function unclear and 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?

There are no parameters and the schema coverage is 100% (empty). The description does not add meaning beyond the schema; it fails to explain what the 'guide' entails or how to use the tool effectively.

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 says 'Guide for sending keyboard shortcuts with pikvm_shortcut' but does not specify if the tool actually sends a shortcut or provides guidance. It lacks a clear verb and resource, making it vague and easily confused with siblings like 'pikvm_shortcut'.

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 given on when to use this tool versus alternatives such as 'pikvm_shortcut' or other keyboard-related tools. The description does not mention prerequisites, limitations, or comparative use cases.

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