SSH MCP Server

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

With no annotations provided, description carries full burden and discloses critical constraints: 'Enforces path policy, blocked extensions, and size limits' and 'Risk level: medium-high (requires user confirmation).' Could improve by noting whether transfers are atomic or overwrite behavior.

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?

Six sentences with zero waste. Logical progression from purpose → constraints → conditional requirements → prerequisites → risk classification. Front-loaded with core functionality.

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 6 parameters with 0% schema coverage and existence of output schema (covering return values), the description successfully documents behavioral constraints, security policies, and parameter interdependencies. Minor gap: does not enumerate direction values (upload/download).

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?

Excellent compensation for 0% schema description coverage. Explains semantics of justification (required for downloads), local_path (source for uploads), session_id (reuse persistent connection), and implies direction values. Missing explicit description of host_id format and remote_path semantics.

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?

Opens with specific verbs ('Upload or download') and clear resource ('file'), immediately distinguishing it from sibling command execution tools (run_ssh_command) and connection management (ssh_connect). The bidirectional nature is explicit.

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?

Provides strong conditional guidance: 'Downloads require a justification string' and 'For uploads, provide local_path.' Explicitly references prerequisite sibling tool ssh_connect for session_id. Lacks explicit contrast with sftp_delete for deletion scenarios.

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