ssh_upload_file

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

With no annotations, the description is solely responsible for behavioral disclosure. It only states the basic upload action, omitting details such as overwrite behavior, error handling (connection failure), permission requirements, or impact on remote directories. Schema parameters cover createDirs but description adds no behavioral context beyond the action.

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 of 9 words with no redundant information. Every word serves to convey the core function.

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 the absence of output schema and annotations, the description is insufficient for an agent to fully understand the tool's behavior. Missing details include: behavior on existing file, size limits, success indication, error scenarios, and relationship to connection lifecycle. A more complete description is needed for a 4-parameter tool.

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 each parameter (localPath, remotePath, connectionId, createDirs). The description does not add extra meaning or explain parameter relationships (e.g., createDirs prerequisite of remotePath parent existence). Baseline score of 3 is appropriate.

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 'Upload a file to the remote server via SFTP' uses a specific verb and resource, clearly stating the action and destination. It distinguishes from sibling tools like ssh_download_file (download) and ssh_execute (execute commands).

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 lacks guidance on when to use this tool versus alternatives like ssh_upload_and_execute. It does not mention prerequisites (e.g., requiring an active connection via ssh_connect) or disclaimers about file overwriting, leaving the agent without clear usage context.

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