ssh_session_stop

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

The description gives no insight into side effects, requirements, or outcome. With no annotations, this leaves the agent without crucial information about what 'stop' entails.

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 extremely short and gets to the point, but it sacrifices valuable information. It is not verbose but is arguably under-specified.

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 tool with one parameter and no output schema, the description is too minimal to guide correct usage. It omits prerequisites, behavior, and return information.

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 schema includes one required parameter, session_id, but the description completely omits it. Since schema description coverage is 0%, the description fails to compensate.

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 (stop) and the resource (SSH session), making it distinct from sibling tools like ssh_session_start and ssh_session_status. However, it lacks any elaboration on scope or effects.

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 when-to-use or alternative comparisons are provided. The description does not mention when to invoke this tool versus other session-related tools.

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