tmux_select_window

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'switch', which is vague and does not explain what happens operationally (e.g., whether the window becomes active, changes current session, or errors on invalid targets). No side effects or failure modes are mentioned.

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 concise sentence, front-loaded with the core action. It contains no fluff or redundant statements. While minimal, it is not a tautology and earns its place, though it sacrifices detail for brevity.

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 tool has no annotations and no output schema, the description is insufficient for a complete understanding. It does not explain what 'switch' entails in tmux terms, such as changing the active window or session context. A user would need prior tmux knowledge to use this correctly.

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?

The input schema fully describes the single parameter 'target' with format 'session:window', resulting in 100% schema description coverage. The description adds no additional information beyond the schema, so the baseline score of 3 is 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 'Switch to a window' uses a specific verb and resource, clearly indicating the tool's action. It implicitly distinguishes from siblings like tmux_select_pane by naming 'window' as the target. However, it lacks explicit scope or context (e.g., 'in the current session') making it not fully comprehensive.

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?

There is no guidance on when to use this tool versus alternatives like tmux_list_windows or tmux_select_pane. The description does not mention prerequisites, such as needing an existing session, or exclusion scenarios. The intended usage is only implied by the name.

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