ssh_interactive_list

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

No annotations are provided, so the description carries the full burden. It states it's a list/read operation implicitly, but does not disclose behavioral traits like whether it returns session IDs usable by ssh_interactive_close or ssh_interactive_input, whether results are cached, or any privacy/sensitivity considerations about displaying session metadata.

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?

A single sentence, zero waste. Every word contributes to the purpose. For a zero-parameter listing tool, this is appropriately brief and front-loaded.

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?

For a simple zero-parameter list operation with no output schema and no annotations, the description is adequately minimal. However, given no output schema, it does not hint at what the returned list contains (session IDs? hostnames?), which an agent would need to chain with ssh_interactive_close or ssh_interactive_input. The description is complete for the operation but leaves return-format guessing to the agent.

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 and the schema coverage is 100% (empty properties), so there is nothing for the description to add. A baseline of 4 is appropriate for a no-parameter tool since parameter semantics are trivially complete.

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 currently open interactive SSH sessions' has a clear verb (list) and resource (open interactive SSH sessions). It distinguishes from sibling tools like ssh_exec, ssh_exec_result, and ssh_ping which are operational/status tools, so the purpose is reasonably clear despite being brief.

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 explicit guidance on when to use this vs alternatives. It does not mention that it pairs with ssh_interactive_close or when one would call this (e.g., before closing sessions or checking active ones). The name and description imply usage but no alternatives or exclusions are given.

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