ssh-session-close

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

The description mentions 'immediately' and 'remove from the MCP server', which gives some behavioral insight. However, it does not disclose potential side effects (e.g., terminating foreground processes, unsaved data loss) or any authorization requirements. Since no annotations are provided, the burden is on the description, which is only partially met.

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, well-structured sentence that immediately conveys the core purpose. It contains no filler or redundant information, making it highly concise 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 destructive action with no output schema, the description covers the essential action but lacks context on success/failure messages, error states, or post-conditions. Additional details about what happens after closing (e.g., session resource freed) would improve completeness.

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 input schema already describes the parameter with 100% coverage, including its type, default behavior, and acceptable values. The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 uses a specific verb 'Close' and identifies the resource as an 'interactive SSH PTY session'. It also clarifies the effect ('immediately and remove from the MCP server'), which clearly distinguishes this tool from sibling tools like ssh-session-open or ssh-session-send.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no warnings about when not to use it. For a session-closing tool, explicit context about active sessions or safety checks would improve usability.

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