qemu_media_set_boot

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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description discloses important behaviors: the boot order change is 'persistent', the VM 'must be stopped' (fails otherwise), and the VM 'remains locked by this session; call vm_unlock when finished.' These add significant operational context not captured 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?

Two short sentences, front-loaded with the main action. No filler or redundant information. Every clause adds value.

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 tool with two parameters and no output schema, the description covers the core purpose, precondition, and side effects. It does not detail error handling or return values, but these are not essential given the tool's simplicity and the presence of annotations.

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 description explicitly maps the 'device' parameter to 'disk, cdrom, or network,' which aligns with the enum in the schema. It does not mention vm_id, but the schema pattern already defines its format. Given 0% schema description coverage, the description partially compensates by explaining the allowed values.

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 tool's function: 'Set persistent QEMU boot order to disk, cdrom, or network.' It uses a specific verb ('set') and resource ('QEMU boot order'), and the three options distinguish it from siblings like qemu_media_mount or qemu_vm_start.

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 provides explicit preconditions: 'The VM must be stopped' and a required follow-up action: 'call vm_unlock when finished.' This gives clear context for when and how to use the tool, though it does not mention alternative tools or exclusions.

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