Keep SSH session alive

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

Without annotations (readOnlyHint=false, etc.), the description carries the burden of behavioral disclosure. It does not explain what side effects occur, such as sending a keepalive packet, extending a timeout, or requiring an already-established session. It fails to mention any prerequisites (e.g., an active session must exist) or failure modes.

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 very short and to the point, but it is not front-loaded with actionable difference. It repeats the name and title almost verbatim ('Keep SSH session alive' vs 'Keep SSH session alive'), which is redundant. However, it is concise and avoids unnecessary detail.

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 absence of output schema and low parameter documentation, the description is insufficient. An agent would not know whether this tool requires an existing session, how to retrieve the sessionId, or what it returns. The simplicity of the tool does not excuse the missing context.

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' is not documented in the schema (coverage 0%), and the description does not explain what it represents, how it is obtained, or its format. The description says 'Keeps an active SSH session alive' but does not connect this to the sessionId, leaving the agent guessing about the parameter's role.

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 states the verb 'keep alive' and the resource 'SSH session', making the purpose clear. It is distinguished from siblings like disconnect and connect by the 'keep alive' action, but it does not explicitly contrast with them, which would have made it clearer.

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 implies that the tool is used to maintain an active session, but it does not specify when to use it versus alternatives like 'termix_docker_keep_ssh_session_alive' or when it should not be used. It lacks guidance on how often to call it or its role relative to session establishment and termination.

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