ssh_sessions

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not indicate whether the operation is read-only, what information is returned, whether it requires active sessions, or any side effects. The description is essentially a restatement of the tool name, providing no additional behavioral insight.

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, concise sentence: 'List SSH sessions.' It is front-loaded, direct, and contains no extraneous information, making it optimally concise.

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?

Despite having no parameters, the tool lacks an output schema and annotations, and the description provides no context about what constitutes an SSH session, how to interpret results, or how this differs from ssh_session_status. The minimal wording leaves significant gaps for an AI agent trying to decide when and how to use it effectively.

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 tool has zero parameters, so there is no parameter semantics to clarify. Per the baseline, a zero-parameter tool earns a 4 because no additional description is necessary for parameter understanding.

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 'List SSH sessions' uses a specific verb and resource, clearly indicating the tool's core function. However, it does not differentiate from sibling tools like ssh_session_status, which might also list or report on sessions, so it misses the distinguishing context that would merit a 5.

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 ssh_session_status or msf_session_list. The description simply states the function without any context, exclusions, or options, leaving the agent to guess the appropriate use case.

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