vm_guest_exec

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

Annotations provide readOnlyHint=false and destructiveHint=false. The description adds that it requires VMware Tools and that output is not captured directly, but does not disclose potential risks of arbitrary command execution or timeout behavior.

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 front-loaded with the purpose, includes a prerequisite, return fields, and a practical note with example. It is concise but the note could be slightly condensed.

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?

Given no output schema, the description lists return fields (exit_code, stdout, stderr, timed_out) and explains the output limitation. However, it omits details on command timeout duration and possible output truncation.

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%, but the description includes an Args section with brief descriptions for all 7 parameters, adding meaning beyond the plain schema (e.g., 'Full path to program' for command). Defaults are mentioned for username.

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 starts with '[WRITE]' and clearly states 'Execute a command inside a VM via VMware Tools,' providing a specific verb and resource. It distinguishes from siblings like vm_guest_download by explaining that output is not directly captured.

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 notes the prerequisite (VMware Tools running), provides an example of capturing output via vm_guest_download, but does not explicitly mention when not to use this tool or alternatives like vm_guest_exec_output.

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