host_pull_to_shared

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

The description adds value beyond the annotations by disclosing the transfer mechanism: resumable rsync with SCP fallback. With destructiveHint=true already declared, it is not required to restate destructiveness, but it does not clarify overwrite behavior or what exactly happens to existing files in the destination.

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?

Two tightly written sentences. The primary purpose is front-loaded, and the fallback mechanism is stated second without any filler. Every word earns its place.

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?

The presence of an output schema and annotations covers return values and the destructive safety profile. The description covers the core operation and transfer fallback. However, parameter semantics remain thin for shared_path and full_output, and overwrite/destination behavior is left ambiguous, so it is not fully complete.

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 for the five undocumented parameters. It gives a high-level mapping between host workspace and shared workspace, which helps with remote_path/shared_path, but it does not explain host_id, timeout, or full_output. This is insufficient given 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 names a specific verb ('Pull'), a clear resource ('file or directory'), and explicit source/destination pair ('one host workspace' -> 'local shared workspace'). This directly distinguishes it from the opposite-direction sibling host_push_from_shared.

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 clearly conveys the intended use case: copying from a host workspace into the local shared workspace. It does not explicitly name alternatives or state when not to use it, but the directional wording provides enough context to route an agent.

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