sftp_download

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

No annotations are provided, so the description carries the full burden. It discloses two important behaviors: automatic file vs directory detection and recursive directory downloads. However, it does not mention overwrite behavior, local directory creation, or failure semantics, which would add useful context for a file-writing operation.

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?

Three short sentences with no filler. The primary purpose is front-loaded, followed by the two key behavioral details. Every sentence contributes useful information.

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 simple download tool with fully documented parameters and no output schema, the description covers purpose, direction, and the key recursive directory behavior. It is slightly light on overwrite/error expectations, but an agent has enough context to select and invoke the tool correctly.

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%, with all three parameters already documented as absolute paths or the connection ID. The description adds file/directory behavior and recursion context, but does not need to repeat parameter definitions since the schema already covers them.

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 ('Download'), resource ('remote file or directory'), target ('local machine'), and transport ('SFTP'). The automatic file-vs-directory detection and recursive directory behavior clearly distinguish it from siblings like sftp_read, sftp_list, and 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?

The directionality ('remote... to local machine') makes the intended use obvious relative to upload/read/list operations. It does not explicitly name alternatives or exclusion conditions, but the use case is clear enough for an agent to decide when to invoke it.

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