mcp-ssh

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action 'disconnect' without explaining what happens (e.g., whether the session is terminated immediately, if data is lost, if it requires specific permissions, or what the response looks like). This leaves critical behavioral traits unspecified.

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 a single, efficient phrase in Russian, which is appropriately concise. However, it's under-specified rather than optimally structured—it lacks front-loaded critical details, but it doesn't waste words on irrelevant information.

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 complexity of a disconnection tool (which may involve session termination and potential side effects), no annotations, no output schema, and incomplete parameter documentation, the description is completely inadequate. It doesn't cover behavioral aspects, usage context, or parameter meaning, leaving the agent with insufficient information to use the tool correctly.

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?

The input schema has 1 parameter (sessionId) with 0% description coverage, meaning the schema provides no details about this parameter. The description adds no information about what sessionId is, how to obtain it, or its format, failing to compensate for the lack of 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?

The description 'Отключение SSH сессии' (Disconnect SSH session) restates the tool name 'ssh_disconnect' in Russian, making it essentially tautological. It doesn't specify what resources are affected or how the disconnection works, though it does include the basic verb 'disconnect' and resource 'SSH session'.

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. Given sibling tools like ssh_connect, ssh_exec, and ssh_list_sessions, the description doesn't explain when disconnection is appropriate (e.g., after execution, to free resources) or differentiate it from other session management tools.

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