Detach from Terminal Session

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

Annotations already indicate mutation (readOnlyHint=false), non-destructive behavior, and non-idempotency. The description adds useful behavioral context by explaining that detachment is recorded on the event stream and does not close the Session for other clients, though it does not elaborate on idempotency or auth requirements.

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 efficient sentence that front-loads the action and follows with the key distinction from terminal_close. Every clause carries useful selection or behavioral information.

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?

The tool is relatively simple, the schema fully documents parameters, and an output schema exists. The description sufficiently explains the operation and its non-closing semantics, though it could optionally mention actor relevance or event-stream implications in more detail.

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 description coverage is 100%, so both session_id and actor are already documented in the schema. The description does not add parameter-level meaning beyond what the schema provides, making the baseline score 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 states a specific verb and resource: record one client detachment on the Session event stream. It immediately distinguishes the action from terminal_close by clarifying that this does not close the shared Session for everyone.

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?

It explicitly gives the condition for this tool—detaching one client without affecting others—and names the alternative terminal_close for closing the shared Session for everyone. The boundary between the two sibling tools is unambiguous.

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