usb_drive_download

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

With no annotations, the description carries the full burden; it usefully discloses that local_path writes to the machine running the MCP server and that inline returns are capped at 100 KB for text files. It omits important behavior: what happens for binary or oversized files without local_path, whether an existing local file is overwritten, and any auth/permission requirements.

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 sentences, front-loaded with the core action and then the mode split; no filler and every clause carries information the agent needs.

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?

An output schema exists, so return-value detail is not required, and the local vs inline distinction is covered. However, the unexplained switch_to_kvm parameter and the unstated behavior for large/binary downloads leave real gaps for a 3-parameter tool.

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% and title-only fields convey nothing. The description meaningfully explains local_path (and its dual mode), but remote_path is never described and switch_to_kvm is entirely undocumented in both the description and the schema, leaving a hidden parameter whose effect an agent cannot infer.

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?

States a specific verb (read/download) and resource (a file from the Virtual USB Drive), which cleanly separates it from usb_drive_upload, usb_drive_list, and usb_drive_delete in the sibling set. An agent knows exactly what the tool produces without opening the schema.

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?

Explains the two operating modes clearly: pass local_path to save to disk on the MCP host, omit it to get small text files returned inline. It stops short of saying when this tool is preferable to alternatives (e.g., checking usb_drive_list first, or that binary/large files require local_path), so there is context but no explicit alternatives or exclusions.

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