Ensure/attach remote tmux session

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

With no annotations provided, the description carries the full burden. It discloses core behaviors: 'ensure the remote tmux session exists (create if missing)' and 'set it as default.' However, it does not explain what 'set as default' entails, whether it attaches to the session (despite the title saying 'attach'), or any side effects or prerequisites.

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 that front-loads the key inputs ('Given an ssh host alias and session name') and clearly states the two actions. It is concise with no unnecessary 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?

The tool has no output schema and no annotations, so the description must compensate. It explains the core functionality and inputs but omits details such as return value, error behavior, or what happens if the session already exists. For a moderately complex remote operation, it is adequately descriptive but not fully complete.

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 the baseline is 3. The description reiterates 'host alias' and 'session name' from the schema but does not add additional meaning beyond what the property descriptions already provide. The optional 'command' parameter is not elaborated upon beyond the schema.

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 tool's action: 'ensure the remote tmux session exists (create if missing) and set it as default for subsequent commands.' This is a specific verb+resource (ensure/attach remote tmux session), and it distinguishes from siblings like tmux_new_session and tmux_set_default by combining remote host aliases with session creation and default-setting.

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 provides clear context: it is used when given an 'ssh host alias and session name' to ensure a remote tmux session exists and set it as default. It does not explicitly state when not to use it or mention alternatives, but the remote host alias makes the intended use case unambiguous.

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