transfer_file

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

With no annotations provided, the description carries the full burden. It discloses the SFTP protocol and direction semantics, but omits important behavioral aspects such as authentication requirements, overwrite behavior, failure handling, and whether the server must be previously configured. This is a network operation, so these gaps are significant.

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, front-loaded sentence that states the core function and then explains direction usage. Every word earns its place, with no unnecessary detail or repetition.

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 tool has 5 parameters and no output schema. The description covers the primary purpose and direction semantics but misses some context like server prerequisites (e.g., server must exist in list_servers), overwrite behavior, and response/status information. Overall, it is reasonably complete for a simple file transfer but leaves a few 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?

The schema covers 100% of parameters, but the description adds value by clarifying that 'upload' means send from local to remote and 'download' means receive from remote to local, which the schema enum alone does not explicitly state. Other parameters rely on schema descriptions, so the net contribution is moderate.

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 transfers files between local and remote via SFTP, with a specific verb and resource. It distinguishes itself from sibling local file tools (read_file, write_file) by explicitly mentioning the remote server and SFTP.

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 context about the tool's function and explains the direction parameter, but it does not explicitly state when to use this tool versus alternatives like read_file or write_file, nor does it mention any exclusions. Usage is implied rather than explicitly guided.

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