ssh_session_close

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

With no annotations, the description fully discloses behavior: terminates the session, writes exit, discards history/context, makes session ID unusable, destructive to session state, not to remote files, 'all' effect, and that the underlying connection is preserved. This is comprehensive.

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 paragraph that front-loads the main action and provides essential details without redundancy. Every sentence adds value, making it concise yet informative.

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 tool with one parameter and no output schema, the description completely covers functionality, side effects, special values, and what it does not do. An agent has all necessary information to decide and use it 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 single parameter 'session' has a schema description indicating ID or 'all'. The description adds that the session ID becomes unusable and explains the 'all' behavior, which goes beyond the schema. Since schema coverage is 100%, baseline is 3, and the added context justifies a 4.

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 clearly states the action 'Terminates an open SSH session' with the resource being the session ID. It distinguishes from sibling tools like ssh_session_start and ssh_session_list by specifying termination. The special value 'all' is also noted.

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 provides context on when to use: to close a session, with behaviors like writing exit, discarding history, and not deleting files. It notes that 'all' closes all sessions ignoring errors. However, it does not explicitly state when not to use or mention alternatives.

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