disconnect

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

With no annotations, the description carries full burden. It discloses key behaviors like terminating background commands, closing PTYs, and terminating sockets. However, it omits idempotency details or what happens if the session is already disconnected. Still, it provides solid behavioral context.

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 concise: two short paragraphs with clear front-loading of the action, followed by argument and return details. Every sentence adds value with no redundancy.

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?

Given the tool's simplicity and the presence of an output schema (implied by return description), the description covers the main purpose, parameter, and return value. It could mention one-time-use or idempotency, but overall it's complete enough for a cleanup tool.

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 0% (only type and title), but the description adds: 'The unique session identifier returned by connect_ssh or create_local.' This clarifies the parameter's origin and purpose, compensating for the lack of schema descriptions.

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 'Disconnects from the active session (SSH or local) and cleans up all associated resources,' specifying the verb and resource. It differentiates from sibling tools like connect_ssh and create_local by focusing on teardown.

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 explicitly ties the session_id to values returned by connect_ssh or create_local, implying it should be used after session creation. It doesn't explicitly state when not to use, but the intent is clear. A slight improvement could be adding explicit 'when to use' instructions.

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