winrm_download

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

Annotations flag destructiveHint=true and openWorldHint=true, and the description meaningfully refines this: existing local files are preserved unless overwrite=true, so the destruction risk is conditional and opt-in. It also discloses the operator-controlled gate on file transfer, which no annotation conveys. Return behavior is not described, but an output schema exists to cover that.

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 with zero filler; the destination constraint and the transfer-disabled caveat are front-loaded ahead of the overwrite default.

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 output schema relieves it of explaining return values, and the overwrite/transfer-gating semantics are well covered. However, a six-parameter tool with a nested connection object and host-selection parameters leaves three or four inputs entirely undocumented, which is a meaningful completeness 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 description coverage is 0% across six parameters, and the description only explains overwrite and constrains local_path to a fixed root. remote_path, connection, saved_host, and inventory_scope receive no explanation anywhere, so an agent has little basis for populating connection or saved_host.

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 and resource ('Copy a file from the Windows host') and makes the direction explicit by naming the destination as WINRM_MCP_LOCAL_ROOT/local_path. That directional statement is what separates it from winrm_upload without naming the sibling.

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?

Gives a real precondition — file transfer is disabled unless the operator enables it — plus the default behavior when a local file already exists. It stops short of explicitly routing the agent to winrm_upload for the opposite direction or to winrm_execute_cmd as an alternative.

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