ssh_file_transfer

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that remote_copy uses scp/rsync and avoids local relay, which is useful. But it does not mention authentication fallback behavior, that delete/write/overwrite operations are destructive, or what the tool returns after an 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?

The description is two sentences, front-loads the core purpose, and then lists operations efficiently. Every phrase earns its place; there is no fluff or redundant restating of parameter names.

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 tool with 16 parameters, 9 directions, no annotations, and no output schema, the description is serviceable but not complete. It gives a good operation catalog but leaves out connection/session selection context, authentication expectations, destructive-operation warnings, and return-value behavior, which an agent would need to invoke it correctly across all modes.

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 schema already documents every parameter. The description adds a little context around write and remote_copy, but it largely stays at the operation-catalog level rather than adding meaning beyond the schema.

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 opens with a clear verb-resource pair: 'Transfer and manage files between local and remote server via SFTP.' It then enumerates the exact operations, making the tool easily distinguishable from sibling tools like ssh_execute or ssh_session.

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 operation list implies when the tool is appropriate for file transfer and management, and the remote_copy note gives a small usage hint about avoiding local relay. However, it never explicitly contrasts this tool with alternatives such as ssh_execute for running commands or ssh_session for session management.

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