install_guest_agent_ssh

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

No annotations provided, so description carries full burden. Discloses destructive nature, password visibility in logs, confirm flag behavior (preview when false), and sshpass requirement. Goes beyond basic mutation disclosure.

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?

Well-structured with a clear warning, prerequisites, and an args list. Every sentence serves a purpose, and the DESTRUCTIVE warning is front-loaded for immediate 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 complex tool with no annotations, the description covers prerequisites, all parameter semantics, security considerations, and execution behavior. An output schema exists, so return values are not required. This is complete for an agent to use correctly.

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 has 0% description coverage, but the description explains every parameter with meaningful detail: vm_ip source, os_family values and default, confirm execution behavior, and password security warning. Adds significant value beyond the schema.

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?

Clearly states it installs QEMU guest agent on a VM via direct SSH, distinguishing it from the sibling install_guest_agent_virsh. The DESTRUCTIVE label and 'via direct SSH' provide method-specific clarity.

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?

Specifies prerequisites: VM must be running and SSH-accessible, and sshpass must be installed. Does not explicitly mention when not to use or compare to the virsh alternative, but context strongly implies this is for SSH-based access.

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