ssh_download_file

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

Beyond annotations (not read-only, not destructive, idempotent, open world), the description adds that local parent directories are automatically created and indicates return format (success with byte count or error). It does not specify overwrite behavior, but no contradictions with annotations.

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 well-structured: a concise summary, behavioral note, parameter details, return description, and examples. It is front-loaded with the main purpose, and every part adds value without fluff.

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 description covers parameter semantics, automatic directory creation, return format, and examples. It does not discuss overwrite behavior or authentication, but given idempotentHint and sibling tools for host management, these are not critical gaps.

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?

With 0% schema coverage, the description fully compensates by providing clear semantics: alias is source host alias, remote_path is absolute POSIX path, local_path includes format differences across OS and advice on calling ssh_get_local_info. Examples further clarify usage.

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 clearly states the tool downloads a file from a remote SSH host to the local machine via SFTP, specifying direction and method. It distinguishes from siblings like ssh_read_file (content reading) and ssh_upload_file (uploading), and includes automatic local directory creation.

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?

The description advises calling ssh_get_local_info for path format guidance and provides examples. It implicitly suggests when to use (file transfer from remote to local) but does not explicitly exclude scenarios or contrast with alternatives.

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