NanoKVM MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that the tool performs a mounting action (implying a state change/mutation) and describes the effect on the target machine, but lacks details on permissions, side effects, error conditions, or rate limits. The description adds some behavioral context but is incomplete for a mutation tool with zero annotation coverage.

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 appropriately sized and front-loaded: the first sentence states the core purpose, the second adds important behavioral context, and the 'Args' section efficiently documents parameters. Every sentence earns its place with no wasted words, and the structure is logical and easy 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 that there is an output schema (which handles return values), no annotations, and 2 parameters with 0% schema coverage, the description does well by explaining the tool's purpose, effect, and parameters. However, as a mutation tool with no annotations, it could benefit from more behavioral details (e.g., prerequisites, errors) to be fully complete, though the output schema mitigates some gaps.

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 description coverage is 0%, so the description must compensate. It explicitly documents both parameters ('file' and 'as_cdrom') with clear semantics: 'file' is the 'Path to ISO file on the NanoKVM device', and 'as_cdrom' specifies whether to 'Mount as CD-ROM (True) or USB disk (False)'. This adds essential meaning beyond the bare schema, fully covering both parameters.

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 ('Mount an ISO image') and target resource ('for the target machine'), distinguishing it from sibling tools like 'nanokvm_unmount_iso' (which performs the opposite action) and 'nanokvm_list_images' (which only lists images). The verb 'mount' is precise and the resource 'ISO image' is well-defined.

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 clear context by explaining that the mounted ISO will appear as 'an attached CD-ROM or USB disk' to the target machine, which helps understand when to use this tool for virtual media attachment. However, it does not explicitly state when not to use it or name alternatives (e.g., when to use 'nanokvm_unmount_iso' instead), though the sibling tool names imply a complementary relationship.

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