tmux_select_pane

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and target format, without explaining side effects (e.g., changing the active pane), prerequisites, or error behavior for invalid targets. The mutation-like nature of 'select/focus' is implied but not elaborated.

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 sentence plus a short Args section, with no redundancy. The purpose is front-loaded, and the examples are efficient. Every element earns its place.

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?

For a simple one-parameter tool with an output schema, the description is minimally adequate. It specifies the target format but omits context about prerequisites (e.g., existing session/window), failure behavior, or the effect on the tmux session. While not severely lacking, it leaves gaps that could affect correct usage.

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 provides no description for 'target' (0% coverage). The description compensates by explaining 'Pane target' and giving concrete examples ('session:window.pane', '%3'), which adds meaningful context beyond the schema's bare type and title.

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 selects/focuses a specific tmux pane, which is a precise action on a specific resource. It distinguishes from siblings like tmux_select_window by explicitly focusing on panes, and the target examples reinforce specificity.

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 implies the tool is used when one needs to focus a pane, but it does not explicitly state when to use it vs. alternatives like tmux_select_window or tmux_list_panes. No conditions, prerequisites, or exclusions are provided, so usage is only implicitly indicated.

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