tmux_stream_resize

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

With no annotations, the description carries the full burden. It discloses that the size sticks across auto-reconnects and returns a specific object. It does not mention destructive effects or prerequisites, but the operation is clearly a resize and likely safe. Overall, it provides sufficient behavioral insight.

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 extremely concise, consisting of two sentences and a return specification. Every sentence provides essential information: the action, the use case, persistence behavior, and output format. No wasted words.

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 simplicity of the tool (3 parameters, no output schema, no annotations), the description covers the core functionality, use case, and output. It does not explain error conditions or parameter constraints, but for a resize operation, this level of detail is likely sufficient for an agent.

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 the description must compensate. It mentions width and height in the context of the resize operation and in the return format, implying their meaning. However, it does not explicitly define each parameter (e.g., that stream_id is the target stream). This is adequate but leaves some ambiguity.

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 verb 'Set' and the resource 'stream's control-client size', and provides a specific use case for when pane output wraps at the wrong width. It distinguishes itself from sibling stream tools (list, read, send, start, stop) by focusing on resizing.

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?

Explicitly states 'Use this when pane output wraps at the wrong width', giving a clear condition for when to invoke this tool. It also mentions the default size (80x24) and that the size persists across reconnects, providing context for usage.

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