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 mentions the basic behavior (download) and the overwrite parameter, but does not disclose error handling, authentication requirements, or idempotency. This is adequate 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 extremely concise with only two sentences. It front-loads the purpose and provides essential parameter guidance without any fluff. Every sentence earns its place.

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 8 parameters, no annotations, and no output schema, the description is insufficient. It does not explain what the function returns (e.g., success message, file path), error scenarios, or prerequisites like needing an active connection. The user is left to infer important details from the schema alone.

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 covers 100% of parameters, so baseline is 3. The description adds value by explaining the usage of 'alias' vs 'host' and the optionality when single connection, but does not provide additional semantics beyond what is in the schema for other parameters like 'remotePath' and 'localPath'.

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's action ('下载文件从远程服务器到本地' - download files from remote server to local) and distinguishes it from sibling tools like sftp_upload (upload) and sftp_ls (list). The verb 'download' is specific and the resource 'file' is explicit.

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 provides clear guidance on when to use 'alias' vs 'host' and notes that parameters can be omitted when there is a single connection. However, it does not explicitly state when to avoid this tool in favor of alternatives like sftp_ls or sftp_mkdir.

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