disconnect

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions returning a disconnection status but fails to disclose potential side effects such as terminating the session, closing active channels, or behavior when the session ID is invalid.

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 appropriately brief and front-loaded with the purpose, followed by a structured Args/Returns format. It contains no wasted words, though it could include more detail in other dimensions.

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, the description includes a return status but lacks behavioral context and usage guidance. Given the absence of annotations and output schema, the agent has limited information about the tool's side effects and lifecycle implications.

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 description merely restates the parameter name ('session_id: Session ID to disconnect') without adding meaningful context beyond the schema. It does not explain where to obtain the session ID or any constraints on its format.

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 ('Disconnect from SSH server') with a specific verb and resource, making it easy to distinguish from sibling tools like connect, execute, and list_sessions.

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 purpose implies the tool should be used to end an SSH session, but there is no explicit guidance on when to use it versus alternatives or prerequisites like having an active session. The context is implied rather than stated.

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