MCP SSH Manager

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

No annotations are provided, so the description carries full burden. While it mentions 'kill' implying destructive action, it doesn't disclose critical behavioral traits like permission requirements (e.g., sudo access), side effects (e.g., process termination consequences), error handling, or output format. For a tool with potentially destructive operations and no annotation coverage, this is inadequate.

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 perfectly concise - a single, front-loaded sentence that efficiently communicates the core functionality without any wasted words. Every word earns its place by specifying actions and target.

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 this is a multi-action tool (including destructive 'kill' operation) with no annotations and no output schema, the description is incomplete. It should address behavioral aspects like authentication requirements, what 'monitor' entails, output format for different actions, and error conditions - especially critical for a tool that can terminate processes.

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 already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain parameter interactions like how 'filter' works with 'action' or default behaviors). Baseline 3 is appropriate when 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 ('list, monitor, or kill') and resource ('processes on remote server'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ssh_execute' or 'ssh_monitor' that might also interact with processes, missing full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'ssh_execute', 'ssh_monitor', and 'ssh_service_status' that might overlap in process management, there's no indication of when this specific tool is preferred or what its scope limitations are.

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