skill_send_key

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

Annotations declare readOnlyHint=true, implying no mutation, but the description says 'sending keys', which is a write operation. This is a clear contradiction. No additional behavioral details are provided beyond annotations.

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?

Extremely short but under-specified. 'Guide for sending keys with pikvm_key' is not informative; it sacrifices clarity for brevity. Every sentence should earn its place, but this single sentence fails to convey purpose.

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 zero parameters and no output schema, the description fails to explain what the tool does, its return value, or prerequisites. It is completely inadequate for an agent to understand and invoke the tool correctly.

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 has zero parameters, so coverage is 100%. The description adds no parameter-specific meaning, but baseline for 0-param tools is 4. There's nothing to describe beyond the schema.

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 'Guide for sending keys with pikvm_key' is vague and tautological, restating the tool name 'send_key'. It lacks a clear verb+resource, and doesn't distinguish from sibling tools like pikvm_key or skill_type_text.

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 on when to use this tool versus alternatives (e.g., pikvm_key, skill_type_text). The description provides no context for appropriate usage or exclusions.

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