sftp_download

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful information about the execution environment ('in-process', 'no scp.exe, no WSL', 'headless') but does not mention side effects like file overwriting, error handling, or authentication precedence. The coverage is partial but not comprehensive.

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, efficient sentence that front-loads the action and destination, then adds a compact caveat about the in-process approach. Every word earns its place with no redundancy.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description could offer more context on authentication modes or path handling, but the schema covers parameters. The in-process detail is valuable, yet the overall picture is only moderately complete for an agent deciding whether and how to use it.

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 100%, so the baseline is 3. The description's mention of 'remote host' and 'this Windows host' loosely aligns with host and localPath, but it adds no additional parameter-level meaning beyond what the schema already provides.

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 uses a specific verb 'Download' with a clear resource 'a file', and specifies source and destination ('remote host' to 'this Windows host'). It also distinguishes from siblings by mentioning 'in-process (ssh2 — no scp.exe, no WSL, headless)', which sets it apart from alternative transfer methods and tools like sftp_upload.

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?

It provides clear context that this is an in-process, headless SFTP download without relying on external executables, implying it should be used when such dependencies are unavailable or undesirable. However, it does not explicitly name alternatives or state when not to use it, so it falls short of full exclusionary guidance.

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