disconnect

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

No annotations are provided, so the description carries the full burden. It adds 'cleanly' as a behavioral qualifier, but does not disclose prerequisites (active session), side effects (what happens to pending data), or error behavior if no session exists. This is a minimal disclosure for a session-terminating operation.

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 with no filler. It is appropriately sized for a zero-parameter action, and every word contributes to the meaning.

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 zero-parameter action with an output schema, the description is mostly adequate, but it omits preconditions and does not contrast with force_cleanup or reconnect. It is not fully complete, though the low complexity keeps the gap from being severe.

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 tool has zero parameters and the description correctly adds no parameter information. The baseline for a zero-parameter tool is 4.

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 resource ('TN3270 session'), and 'cleanly' implies a graceful teardown that contrasts with the sibling force_cleanup. It is immediately clear what the tool does and how it differs from connect/reconnect/force_cleanup.

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 only guidance is 'Close the TN3270 session cleanly,' which implies using it when the agent wants to end a session. It does not explicitly say when to prefer it over force_cleanup or whether it requires an active connection, so the usage context is left to inference.

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