MCP SSH Manager

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

No annotations are provided, so the description carries the full burden. It mentions 'manage connection pool' but doesn't disclose critical behaviors: what 'cleanup' does (e.g., removes idle connections), whether actions like 'reconnect' are destructive or require authentication, or any rate limits. This leaves significant gaps for a tool with multiple actions.

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 concise and front-loaded with the core purpose in a single sentence. However, it could be more structured by explicitly listing the actions or their effects, but it avoids unnecessary verbosity.

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 tool's complexity (multiple actions with varying behaviors) and lack of annotations or output schema, the description is insufficient. It doesn't explain what each action does (e.g., 'cleanup' vs. 'disconnect'), return values, or error conditions, leaving the agent with incomplete context for proper invocation.

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 fully documents parameters. The description adds no additional meaning beyond implying that 'server' is optional for some actions (e.g., 'status' might not need it), but this is already clear from the schema's required fields. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the tool's purpose with specific verbs ('check status' and 'manage connection pool') and identifies the resource (SSH connections). It distinguishes from siblings like ssh_session_list or ssh_session_close by focusing on connection pool management rather than individual sessions, though it doesn't explicitly name alternatives.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools for SSH operations (e.g., ssh_session_list, ssh_session_close, ssh_health_check), the description lacks context on whether this is for monitoring active connections, handling pooled resources, or other specific scenarios, leaving usage ambiguous.

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