tmux_select_layout

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

No annotations; description lacks details on side effects (e.g., rearrangement of panes, destructiveness). Does not disclose behavior beyond applying a layout.

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?

Single concise sentence, front-loaded with key information. No redundancy.

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 3 params, no schema descriptions, and no output schema, the description is incomplete. It omits how to target a specific window, what a layout string looks like, and any prerequisites or results.

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%; description adds meaning for 'layout' (named layouts) but provides no semantics for 'window' or 'target' parameters, which are critical for usage.

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?

Uses verb 'apply' with resource 'layout to a window', lists specific named layouts, and implies distinction from siblings like 'tmux_next_layout'. However, it doesn't explicitly contrast with cycling layouts.

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?

No guidance on when to use vs alternatives (e.g., tmux_next_layout, tmux_resize_pane). Usage is implied but not explicit.

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