SSH MCP Server

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

Annotations are absent, so the description carries full disclosure burden. While it identifies SFTP as the protocol, it fails to disclose whether the operation overwrites existing files, creates parent directories automatically, or how it handles authentication precedence when both password and key are provided.

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 10-word sentence with zero redundancy and proper front-loading. However, given the tool's complexity (multiple authentication methods, path handling), the extreme brevity arguably underserves the user despite being technically concise.

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 7-parameter file transfer operation with complex authentication options (key vs password), no output schema, and no annotations, a 10-word description is inadequate. Missing critical context: overwrite semantics, directory creation behavior, and success/failure indicators.

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 completely documents all 7 parameters including authentication options and paths. The description adds minimal semantic value beyond the schema, only mentioning 'local file' and 'remote host' which correspond to existing parameter descriptions.

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 provides a specific verb (Upload), clear resource (local file to remote host), and mechanism (SFTP). It implicitly distinguishes from siblings like ssh_download (directionality) and ssh_write_file (local file path vs inline content) by emphasizing 'local file' transfer via SFTP protocol.

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 explicit guidance on when to prefer this over ssh_write_file (which likely writes content directly) versus uploading existing local files. No mention of prerequisites like SSH access requirements, file existence checks, or authentication method selection criteria.

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