tmux_open_session

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

With no annotations, the description carries the full burden. It reveals that the session is detached and returns an ID, which is valuable, but it omits details like session naming, error behavior, or whether the command runs interactively. It also doesn't clarify what 'running a command' implies for PTY handling.

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, well-structured sentence with a clear order: action, use case, return value. Every clause earns its place, and there is no redundancy or irrelevant detail.

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?

Despite having 6 parameters, nested objects, and several closely named siblings, the description is minimal. It does not explain how to use the returned session ID for subsequent interactions, nor does it distinguish this tool from open_session or run, leaving significant gaps for a moderately complex 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 only 33% (width/height described), yet the description adds no explanation for cwd, env, args, or command. 'running a command' only hints at the command param, leaving the other 4 params entirely unexplained. This does not compensate for the low schema coverage.

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 function: 'Start a detached tmux session running a command' and mentions a use case (TUI apps) and return value. However, it does not explicitly differentiate from sibling 'open_session', relying on the tmux prefix in the name.

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 provides a clear use case ('useful for full-screen TUI apps like vim/htop') but lacks explicit when-not-to-use guidance or alternatives. It does not mention when to prefer this over 'open_session' or 'run'.

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