nanokvm_mount_iso

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 explains the effect: the target will see the ISO as a CD-ROM or USB disk. However, it does not disclose potential side effects, such as overwriting a previously mounted image, or whether the mount persists until unmounted.

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 concise and well-structured. It leads with the main action, explains the user-visible effect, and lists arguments with brief, useful explanations. Every sentence contributes.

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 two-parameter mount tool, the description provides sufficient context: what it does, what the target sees, and parameter meanings. It does not mention prerequisites (e.g., ensuring the file exists) or that only one image may be mounted at a time, but these are minor 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?

The schema has 0% coverage, but the description compensates by explaining both parameters: 'file' is the path on the NanoKVM device, and 'as_cdrom' distinguishes between CD-ROM and USB disk modes. This adds meaning beyond the bare schema titles.

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 action: 'Mount an ISO image for the target machine.' This uses a specific verb and resource, making it distinct from sibling tools like nanokvm_unmount_iso and nanokvm_list_images.

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 implies when to use the tool: when you want to attach an ISO image to the target machine. It does not explicitly mention alternatives or when not to use it, but the context is clear enough given the sibling tools.

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