qemu_media_eject

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

Discloses side effects beyond annotations: the drive persists as empty for future starts, and the VM remains locked by the session requiring vm_unlock. Annotations provide no positive hints (all false), so the description carries the burden and does so effectively.

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 sentences, no fluff, and the main action is front-loaded. Every clause adds value, including the lock reminder.

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?

Covers the main behavior and a critical side effect (lock). Lacks detail on edge cases like 'if not running' or what happens if no CD-ROM is present, but for a single-param tool with no output schema, it is reasonably complete.

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 coverage is 0%; the description never mentions vm_id. While vm_id is likely obvious as the VM identifier, the description fails to clarify its role or tie it to the tool's action. With a single parameter, the baseline is higher, but the description adds nothing about it.

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 ('Eject the managed CD-ROM'), the resource (CD-ROM), and timing ('now when running'), plus the persistence behavior. This distinguishes it from siblings like qemu_media_mount or qemu_media_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?

Provides clear context: 'when running' and 'persist an empty drive for future starts'. It also warns about the lock and instructs to call vm_unlock. No explicit exclusions or alternatives, but usage context is sufficiently clear.

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