Copy file or directory from Parallels guest to host

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the baseline is lower. The description adds that the operation writes to a host path and supports an optional guest user, but it does not disclose overwrite behavior or prerequisites. This is adequate but not rich.

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 concise and well-structured: a one-sentence purpose, a short use-case line, and a clean Args list. Every sentence adds value and the most important information is front-loaded.

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 5-parameter tool with an output schema and annotations, the description covers the core purpose, all parameter semantics, and typical use cases. It does not mention overwrite behavior or guest prerequisites, but these are partially covered by destructiveHint and are not essential for basic invocation.

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. It explains all five parameters with meaningful context: guest_path is 'inside the guest', host_path is 'on the host where file/folder will be written', user is 'optional guest user to read files as', and timeout_s has a default. This goes beyond the bare 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?

The description states a specific action ('Stream a file or directory from a guest path back to the host filesystem') with a clear resource and direction. It distinguishes itself from the sibling vm_copy_to_guest by explicitly saying 'back to the host', making the direction unambiguous.

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 provides clear use cases: 'Extracts test reports, build artifacts, logs, or files produced inside the VM.' It does not explicitly name alternatives or exclusions, but the directionality and use cases make when to use this tool clear.

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