vm_guest_download

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds a '[READ]' prefix and the prerequisite of VMware Tools. There is no contradiction with annotations. The description provides useful context beyond the annotations by clarifying the tool is a read operation and requires VMware Tools.

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 very concise: a one-line header and a bullet-like list of parameters. Every sentence serves a purpose (purpose, prerequisite, args). No wasted words. Well-structured for quick parsing by an AI.

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 the tool's simplicity, rich annotations, and existence of an output schema (which reduces need to describe return values), the description is minimally adequate. However, it lacks details about behavior when files are missing or permission errors occur, which could help agents handle edge cases. It covers the essential use case but no more.

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%, so the description must compensate. The description lists all parameters in Args but only by name (e.g., 'vm_name: Target VM name.'), adding minimal meaning beyond the property names. It does not explain formats, constraints, or valid values. For a 6-parameter tool with no schema descriptions, this is insufficient to guide correct usage.

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 explicitly states '[READ] Download a file from a VM to local machine via VMware Tools.' It clearly identifies the action (download), the resource (file from VM), and the method (via VMware Tools). Distinguishes from sibling tools like vm_guest_upload (upload) and vm_guest_exec (execute).

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 includes a clear prerequisite: 'Requires VMware Tools running in the guest OS.' This helps agents determine when it is safe to use. However, it does not explicitly state when to use vs. alternatives or provide exclusions. Still, the context is clear enough for a straightforward file operation.

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