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 specific diagnostic behaviors: checks ssh-agent, keys, known_hosts, config, and performs test connection. Deducting one point as it doesn't explicitly confirm read-only safety or describe output format, though 'diagnose' and 'checks' imply non-destructive 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?

Perfectly structured: sentence 1 states purpose, sentence 2 details specific checks, sentence 3 gives usage timing. Zero redundancy; 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?

Strong completeness given 2-param tool with no output schema. Description adequately scopes what gets diagnosed. Minor gap: doesn't hint at return value structure (e.g., whether it returns a report vs boolean), though listed checks imply diagnostic output.

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 coverage is 100% (host and port fully described), establishing baseline 3. Description doesn't add param-specific semantics, but doesn't need to given complete schema documentation.

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?

Excellent specific purpose: 'Diagnose SSH connectivity issues' with specific verb (diagnose) and resource. Clearly distinguishes from operational siblings (ssh_exec, ssh_upload, etc.) by listing diagnostic checks (agent, keys, known_hosts, config) rather than actions.

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?

Exceptional guidance with explicit temporal logic: 'Use this BEFORE attempting SSH operations... or AFTER a failed SSH operation'. Clearly positions the tool relative to alternatives and failure scenarios.

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