tmux_copy_mode

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

No annotations are provided, so the description carries the full burden. It discloses that exit sends the copy-mode cancel command (tmux 2.4+) and describes the return format. However, it does not address potential side effects or behavior when both page_up and exit are true. This is adequate but not exhaustive.

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 (four lines) and front-loaded with the main purpose. Each sentence adds necessary information without redundancy. Technical details are appropriately placed in the second sentence.

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 4 parameters (1 required) and no output schema or annotations, the description covers the core behavior and two key parameters. It lacks explanation for the target parameter and does not explicitly state the nature of the operation (state change). It is adequate but not fully comprehensive.

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 0%, so the description must add meaning. It explains page_up (scrolls up one page on entry) and exit (leaves copy mode), but does not clarify target_pane or target. It provides partial but significant value for two of four parameters.

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 'Enter (or exit) copy mode in a pane.' This is a specific verb-resource pair, and it distinguishes itself from sibling tools like tmux_copy_scroll and tmux_copy_search by focusing on mode entry/exit rather than scrolling or searching.

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 explains the effects of the page_up and exit parameters, helping the agent understand when to use each. It also mentions the return value. However, it does not explicitly contrast with alternatives like tmux_copy_scroll or tmux_copy_search, though the context is fairly self-explanatory.

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