tmux_link_window

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

The description discloses that the window appears in both spots and that select=False links in the background (-d). However, it does not explain the 'target' parameter, and with no annotations provided, the description should cover all behavioral aspects.

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 concise with two short paragraphs, front-loading the purpose in the first sentence. There is no wasted text.

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 description adequately explains the tool's function and main parameters for a specific tmux concept. However, it omits the 'target' parameter and could elaborate on the simultaneous dual-location behavior. An output schema is absent, but return values are not essential for this 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?

The description adds meaning to src and dst with example formats (e.g., 'sess1:2', 'sess2:') and explains select. However, it omits explanation for the 'target' parameter, and schema description coverage is 0%, so the description should compensate more fully.

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 purpose with a specific verb ('link') and resource ('window'), explaining that the window appears in both locations. This distinguishes it from siblings like tmux_unlink_window and tmux_move_window.

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 example syntax for src and dst, and explicitly mentions using tmux_unlink_window to remove a link. However, it does not compare with tmux_move_window or tmux_swap_window to clarify when linking is preferred over moving or swapping.

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