esxi_transfer_read_chunk

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes beyond them usefully by disclosing the 1MiB per-chunk ceiling and the intended concatenation-and-SHA256-verification workflow. It still omits what happens on an incomplete job, bad offset, or checksum mismatch.

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?

A single tight sentence with the core read action front-loaded, followed by the chunk constraint and the workflow. Dense but every clause carries information; minor crypticness in the offset phrasing keeps it from a 5.

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?

With an output schema present, return values need no explanation, and annotations cover safety. The definition supplies the chunking contract an agent needs to reconstruct the file correctly; only edge-case/error behavior for incomplete or mismatched chunks is unaddressed.

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 carries the burden. It partially compensates by explaining offset's role in reassembling chunks and confirming the 1MiB block size (matching the length default), but job_id is never explained and the length/offset defaults are left to the 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 verb and resource: reading already-completed download/staged files as chunks. It also pins the chunk size (1MiB), which distinguishes it from the write-side sibling esxi_stage_write_chunk. It stops short of naming those siblings explicitly, so 4 rather than 5.

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?

Saying the file must be '已完成' (already completed) implies the tool is only for post-download reads and hints at a start-then-read workflow, but no alternative tool is named and no when-not-to-use case (e.g. use esxi_stage_write_chunk for uploads) is given. Usage is inferred rather than stated.

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