下载文件

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

The description adds a specific behavioral detail that local targets may be overwritten if they already exist, which goes beyond the annotations' destructiveHint=true by explaining the overwrite condition. This is consistent with annotations and adds context for the agent.

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 concise sentence, which is structurally efficient. However, it is under-specified for a five-parameter tool, providing only a vague overview. It is not wordy but sacrifices critical information for brevity.

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?

With five parameters, annotations, and an output schema, the description covers only the basic download action and overwrite risk. It omits whether recursive downloads are supported, the purpose of preserve, or the role of alias, leaving significant gaps for an agent trying to 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 0%, and the description does not explain any of the five parameters. It only alludes to 'local target' and 'download file' without clarifying the roles of remote_path, local_path, alias, preserve, or recursive. Parameter meanings are left entirely to name inference.

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 files via SFTP, using a specific verb and resource. This distinguishes it from sibling tools like ssh_upload (upload) and ssh_execute (command execution).

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 implies usage for downloading files from a remote server over SFTP, but does not explicitly state when to use it over alternatives or mention exclusions (e.g., directories). The sibling tool ssh_upload implies the opposite, but no explicit guidance is provided.

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