qemu_media_list

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

Discloses a significant behavioral trait not covered by annotations: the VM remains locked by this session and must be unlocked with vm_unlock. Also clarifies it reports the mounted ISO, adding useful output context.

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 with the purpose front-loaded. Every sentence adds value: the first states the action and scope, the second provides a critical locking caveat. No fluff.

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?

The description covers what the tool lists, what it reports (mounted ISO), and the lock behavior. With no output schema, this sufficiently sets expectations for a read-only listing tool.

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 only parameter vm_id is not described in the schema or description; the description's reference to 'this managed VM' implies its purpose but does not specify format or origin. With 0% schema coverage, the description should compensate more.

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 lists ISO images in a VM's media directory and reports the mounted ISO, distinguishing it from sibling tools like qemu_media_mount or qemu_media_eject.

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 that this is a read-only listing operation and notes the VM remains locked, requiring vm_unlock. However, it does not explicitly mention when to use it vs alternatives or when not to use it.

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