qemu_media_mount

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

Annotations already signal mutation via readOnlyHint=false and idempotentHint=false. The description adds useful behavioral detail: the operation is performed immediately on a running VM and persists across reboots. However, it does not disclose side effects such as replacing an already-mounted ISO, error behavior, or prerequisites beyond the VM running.

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 a single, front-loaded sentence with no wasted words. It states the action, timing, and persistence in one compact statement, making it easy for an agent to parse quickly.

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 tool with two required parameters and zero parameter descriptions, this description is too thin to fully support correct invocation. It explains what the tool does, but not how to supply vm_id or media_id, what happens if media is already attached, or what the response indicates; there is also no output schema to fill that gap.

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 for the undocumented vm_id and media_id parameters. It does not explicitly explain either parameter; only the phrase 'managed ISO' hints that media_id refers to the ISO, and context implies vm_id is the target VM. This leaves parameter meaning and valid value discovery mostly to inference.

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 has a specific verb-resource pair, 'Mount a managed ISO', and adds temporal scope ('now when the VM is running') plus a persistence guarantee ('persist it for future starts'). This clearly distinguishes it from sibling operations like qemu_media_eject, qemu_media_delete, and qemu_media_set_boot.

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 gives clear usage context: use this when the VM is running and you want the mount to survive future starts. It does not explicitly name alternatives or give when-not-to-use guidance, but the context is strong enough to route an agent to the right operation.

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