ssh_stop_session

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

With no annotations, the description carries the burden. It discloses key side effects: session termination, tmux observer cleanup, return of unread output and exit metadata, and preservation of the transcript file. This is more transparent than typical. However, it omits details like default signal (SIGTERM vs SIGKILL) and potential blocking behavior, which are partially covered by the schema.

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, front-loaded sentence delivers all essential information without redundancy. Every clause adds value: termination, observer cleanup, return value, and file preservation. It is 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?

The core behavior is described, but key operational details are missing: parameter semantics for max_output_chars and session_id, return format details, and error handling. Since there is no output schema, the description should provide more specifics. The tool is moderately complex (4 params, no annotations), and the description is adequate but not complete.

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?

Schema coverage is only 50%, and the description does not compensate. It fails to explain the format or purpose of session_id and max_output_chars. The phrase 'final unread output' hints at max_output_chars but does not explicitly connect them. The description adds no meaning beyond the schema.

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 ('Terminate'), the resource ('tracked SSH session'), and additional distinguishing behaviors ('close any attached tmux observer', 'return final unread output plus exit metadata'). This differentiates it from siblings like ssh_stop_forward and ssh_read_session.

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 usage context is implied: it is the tool to stop an SSH session. However, there is no explicit 'when to use' vs alternatives or exclusions. Sibling tools are not mentioned, so the agent must infer when to choose this over similar tools.

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