qemu_vm_command_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds modest value by clarifying that no VM state changes occur and that the output is the exact managed command, but it does not go beyond the safety profile already established by 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?

The description is a single, tightly worded sentence with no filler. It front-loads the core purpose ('Preview') and includes the key safety qualifier immediately, earning its place with every word.

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?

With 12 parameters, nested objects, no parameter descriptions, and no output schema, the one-sentence description leaves major gaps. It does not explain what 'managed QEMU command' means, how parameters relate to the generated command, or what the preview output looks like, making it insufficient for confident invocation.

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%, and none of the 12 parameters are described anywhere. The description provides no meaning for cpus, memory, overrides, profile, acceleration, or other fields, forcing the agent to guess despite the large, nested parameter surface.

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 states a specific verb ('Preview') and a clear resource ('the exact managed QEMU command'), immediately distinguishing this from state-changing siblings like qemu_vm_create or qemu_vm_update. The phrase 'without changing VM state' reinforces its read-only purpose.

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 usage: use this when you want to see what managed QEMU command would be used without mutating VM state. However, it does not explicitly name alternatives or state when not to use it, leaving the routing decision partially to inference.

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