SSH MCP Server

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

No annotations provided, so description carries full burden. Discloses key behavioral traits: keepalive probes, auto-close after idle timeout, return value semantics (session_id), and security posture ('Risk level: low'). Does not cover authentication requirements or error conditions.

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?

Four sentences with zero redundancy. Front-loaded with purpose ('Open...'), followed by return value, lifecycle behavior, and risk level. Every sentence earns its place.

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?

Appropriate for tool complexity (single parameter, output schema exists). Covers connection lifecycle management and integration points with sibling tools. Could mention authentication prerequisites given SSH context, but acceptable without.

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 has 0% description coverage for the single 'host_id' parameter. Description mentions 'to a host' but fails to specify what host_id represents (IP address, hostname, or reference from list_hosts?), acceptable formats, or constraints. Insufficient compensation for schema gap.

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?

Specific verb ('Open') + resource ('persistent SSH session') + scope ('to a host'). Explicitly distinguishes from sibling tools by stating it returns a session_id for 'run_ssh_command' and 'transfer_file', establishing the persistent vs. one-off usage pattern.

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 clear guidance by naming specific sibling tools (run_ssh_command, transfer_file) that consume the output. Mentions 'reuse the connection' implying when to choose this over stateless alternatives. Lacks explicit 'when not to use' exclusions (e.g., short-lived commands).

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