Poll QEMU guest exec status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that it returns exit status and captured stdout/stderr, but does not disclose any additional behavior beyond what annotations provide.

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 a single sentence of 11 words, conveying all necessary information without any extraneous content. It is front-loaded and efficient.

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?

No output schema is provided, so the description should ideally hint at the return structure. It only mentions 'exit status + captured stdout/stderr,' which is adequate but vague for an AI agent expecting a specific JSON format. More detail on the output shape would improve completeness.

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 low (33%), with only 'pid' having a description ('PID returned by vm_agent_exec'). The description adds meaning by clarifying that the pid comes from vm_agent_exec, but provides no additional context for 'node' or 'vmid'. This partially compensates for the low coverage.

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 uses a specific verb 'Return' and clearly identifies the resource: 'exit status + captured stdout/stderr for a previously launched exec.' It unambiguously distinguishes from sibling tools like vm_agent_exec, which launches an exec, and vm_agent_info, which returns general QEMU agent info.

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 states it is for a 'previously launched exec,' clearly implying it should be used after a call to vm_agent_exec. While it does not explicitly list when not to use or name alternatives, the context is sufficiently clear for appropriate selection among siblings.

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