qemu_media_set_boot

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds non-obvious behavioral context: the change is persistent and requires the VM to be stopped. It does not detail side effects on future starts, but the annotation plus persistence note is adequate for this simple setter.

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?

Two short sentences front-load the core action and choices, then state the prerequisite. There is no filler or repetition of schema fields beyond what is useful.

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 two-parameter setter with no output schema, the description is largely complete: it identifies the target VM as a required ID, enumerates the device choices, and gives the critical stopped-state precondition. It lacks only error/return behavior notes, which are not essential for this operation.

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 carry parameter meaning. It explains the 'device' parameter via the boot-target list (disk/cdrom/network) and links it to boot order, but it leaves 'vm_id' semantics to inference from the name and pattern. This is partial compensation, not complete.

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 names a specific action ('Set persistent QEMU boot order'), a target resource (QEMU), and the three allowed values (disk, cdrom, network). It is clear, but it does not explicitly distinguish itself from the many qemu_media_* siblings such as qemu_media_mount/eject/delete.

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?

It clearly states the key prerequisite: 'The VM must be stopped,' which tells an agent when it is safe/valid to invoke this tool. It does not mention alternatives or explicitly say when not to use it, but none of the sibling tools perform boot-order changes.

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