qemu_qmp_execute

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

Annotations are all false and provide no guidance, so the description carries the transparency burden. It discloses a key side effect: the VM remains locked by this session and requires vm_unlock. This is valuable behavioral context beyond the structured fields, although it does not describe return format or potential command side effects.

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 two sentences: the first states purpose, the second gives a critical usage condition. No wasted words, and the lock warning is front-loaded enough to catch attention.

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 generic command execution tool with no output schema and low schema coverage, the description is incomplete. It lacks information about return values, error handling, how to format the command and arguments, and what 'advanced' means. The lock warning is useful but does not fill the main gaps.

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 the description does not explain vm_id, command, or arguments. It only says 'advanced QMP command' without elaborating on how to structure parameters. This leaves the agent without any semantic guidance beyond the parameter names.

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 (Run), the resource (advanced QMP command), and the target (managed VM's local broker-owned QMP endpoint). It is distinct from siblings like qemu_hmp_command (which executes HMP commands) and qemu_vm_command_preview (which likely previews commands).

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 explicitly warns that the VM remains locked by this session and instructs to call vm_unlock when finished, providing important context for use. However, it does not explicitly mention when to use this over alternatives or include exclusions like 'use qemu_hmp_command for simpler HMP commands.'

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