Keep SSH session alive

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

The annotations already convey readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds no behavioral detail beyond restating the title. It does not explain what keeping the session alive entails, what side effects may occur, whether it sends keepalive packets, or what happens to the session. The description provides zero additional transparency.

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 short but not efficiently concise; the two sentences are redundant. 'Keep SSH session alive' and 'Keeps an active SSH session alive' convey the same idea, so the second sentence earns no additional value.

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?

With one undocumented parameter and no output schema, this description is inadequate. An agent cannot determine how to supply sessionId, when the operation is available, whether it is safe to repeat, or how to confirm it succeeded. It also fails to clarify the Docker-specific context versus the similar file-management keepalive tool.

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 single parameter sessionId has 0% schema description coverage, and the tool description makes no mention of it. An agent is not told what sessionId refers to, where to obtain it, whether it is required, or what format it must take. The description does nothing to compensate for the undocumented parameter.

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 is essentially the title restated: 'Keep SSH session alive' followed by 'Keeps an active SSH session alive.' It names the resource and action, but does not distinguish this Docker-scoped tool from the nearly identical sibling termix_files_keep_ssh_session_alive, making it too tautological to be genuinely clarifying.

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?

There is no guidance on when to use this tool versus alternatives such as termix_docker_check_ssh_session_status, termix_docker_establish_ssh_session_docker, or termix_files_keep_ssh_session_alive. The phrase 'active SSH session' weakly implies a precondition, but no concrete usage context or exclusions are provided.

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