Transfer a file from a remote server to a local machine using an SSH connection. Specify remote and local paths to retrieve files securely.
Download file from connected server
| Name | Required | Description | Default |
|---|---|---|---|
| localPath | Yes | Local path | |
| remotePath | Yes | Remote path | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Changes observed during successful MCP inspections.
v1.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states that a file is downloaded from a connected server; it does not mention that localPath will be written, files may be overwritten, or that a valid connectionName is needed. This is a significant gap for a tool with side effects on the local filesystem.
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?
The description is a single, front-loaded sentence with no filler words. However, it may be underspecified for a tool that writes to the local filesystem, so it is not maximally effective.
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?
For a 3-parameter tool with no output schema and no annotations, the description is incomplete. It omits behavioral details such as overwrite behavior and default connection semantics (though connectionName is documented in the schema). An agent would need to infer several operational aspects beyond what is given.
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?
The input schema already contains descriptions for all three parameters (localPath, remotePath, connectionName), and schema coverage is 100%. The description adds no additional parameter-level meaning, so the baseline score applies.
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 the precise operation ('Download file') and the source ('from connected server'), clearly identifying it as a remote-to-local transfer. It is distinct from siblings like upload, execute-command, and list-directory, though it does not explicitly distinguish itself by name.
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?
No guidance is provided about when to use this tool versus alternatives such as upload or list-directory. The description merely restates the operation and leaves the agent to infer selection criteria from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.