tmux_stream_stop

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: detaching the control client, session continuation, connection freeing, and return value. However, it does not mention error conditions or side effects for invalid stream_id.

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?

Two sentences, front-loaded with the action, no extraneous words. Every sentence adds value.

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 one-parameter tool with no output schema, the description explains the tool's purpose, effect, and return format. It could include a usage hint (e.g., 'after starting a stream with tmux_stream_start') but is otherwise adequate.

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%, so description must compensate for the undocumented 'stream_id' parameter. The description only mentions stream_id in the return value, not explaining what it is or how to obtain it. This adds minimal meaning beyond the parameter name.

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 'Stop a stream' with a specific verb and resource. It explains the implications (detach control client, session keeps running, free connection) and mentions the return value, distinguishing it from sibling stream tools like tmux_stream_start.

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 implies usage when a stream needs to be stopped, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any prerequisites or conditions (e.g., stream must be active). Context about when not to use it is missing.

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