ssh_transfer

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

No annotations present, and description lacks behavioral details such as whether files are copied or moved, overwrite behavior, error handling, or that transfers happen server-to-server without client involvement.

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?

Single sentence conveys the core action efficiently with no redundancy.

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?

No output schema, annotations missing, and description fails to explain return values, success/failure signals, or that sessions must be active, leaving significant gaps for a transfer operation.

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 descriptions cover all 4 parameters, but the tool description adds no extra meaning beyond the schema, such as explaining 'session name' or linking to ssh_connect.

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?

Description clearly states it transfers a file between two remote servers via SFTP, distinguishing it from siblings like ssh_download and ssh_upload which involve local machine transfers.

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?

No guidance on when to use this tool vs alternatives, no mention of prerequisites like needing pre-established sessions, and no exclusions provided.

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