esxi_datastore_transfer

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

Adds real behavioral context beyond annotations: dry_run defaults to preview-only, real writes require both a normal and advanced write switch, default no-overwrite protects admin VM directories, URL upload streams large files, download base64 capped at 8MiB, server never reads arbitrary local files. Destructive hint is corroborated by the overwrite caveat. Slightly less explicit on exact size limits for uploads.

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?

Terse and information-dense, mixing Chinese and English. Front-loads the operations, then behavioral caveats. Some phrasing is compressed to the point of ambiguity (e.g., '普通和高级写开关'), which slightly hurts readability.

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 8 parameters, 0% schema coverage, annotations present, and an output schema, the description supplies the key usage and safety context an agent needs. It lacks explicit routing guidance against the many sibling transfer/stage tools, which is the main remaining gap.

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%, so the description carries the burden. It explains data_base64 vs source_url, the 8GiB max_bytes for URL streaming, the 8MiB download cap, dry_run preview semantics, and overwrite behavior. It doesn't cover 'path' or 'datastore' formatting, but compensates well for the documented parameters.

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 clear verb+resource: stat/download/upload of datastore files, and clarifies that upload does not equal deployment completion. It distinguishes itself from siblings like esxi_stage_upload and esxi_transfer_start, though the exact boundary with esxi_transfer_start/esxi_stage_upload isn't spelled out.

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?

It gives context on dry-run default preview, write switches, and no-overwrite default, which implies usage. But with siblings like esxi_transfer_start, esxi_stage_upload, esxi_transfer_read_chunk, it doesn't explicitly say when to choose this tool over those chunked-transfer alternatives.

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