NanoKVM MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the paste API mechanism, character limit constraint (1024 max), and keyboard layout support. However, it doesn't mention error conditions, performance characteristics beyond 'faster,' or what happens with invalid inputs.

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 perfectly structured and front-loaded: the first sentence states the core purpose, followed by implementation details, constraints, and parameter explanations. Every sentence earns its place with no wasted words, making it highly efficient for an AI agent to parse.

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 tool's moderate complexity (keyboard emulation with constraints), no annotations, and the presence of an output schema (which handles return values), the description is nearly complete. It covers purpose, usage guidelines, behavioral traits, and parameter semantics well. The only minor gap is lack of explicit error handling or edge case information.

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?

With 0% schema description coverage, the description must compensate for the schema's lack of parameter documentation. It successfully adds meaning for both parameters: 'text' is explained as 'The text to type' with character limit context, and 'language' is explained with specific examples ('"" for US QWERTY, "de" for German'). This provides essential semantic context beyond the bare 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 clearly states the specific action ('Type text on the target machine via keyboard emulation') and resource ('target machine'), distinguishing it from siblings like nanokvm_send_key (individual key presses) and nanokvm_click (mouse actions). It explicitly mentions the faster paste API, providing clear differentiation.

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 explicitly states when to use this tool ('faster than individual key presses') and provides clear alternatives by naming the sibling tool nanokvm_send_key. It also specifies usage constraints ('Maximum 1024 characters per call'), giving clear guidance on when this tool is appropriate versus alternatives.

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