tmux_copy_scroll

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

With no annotations, the description must fully disclose behavioral traits. It notes the tool may enter copy mode first and details how direction and amount work, but it does not explain side effects (e.g., stays in copy mode?), potential errors, or read-only nature. Transparency is adequate but not comprehensive.

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: a one-line purpose followed by necessary details on direction and amount. It avoids wasted words, though the list of direction values could be seen as dense. Overall, it is efficiently structured and front-loaded.

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 4 parameters (1 required) and no output schema or annotations, the description explains half the parameters (direction, amount) but omits target_pane and target. It also does not mention return values. Completeness is sufficient for a simple scroll action 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%, requiring the description to compensate. It explains 'direction' and 'amount' meaningfully (e.g., direction values, amount ignored for top/bottom), but 'target_pane' and 'target' are left unexplained. This partial coverage meets a baseline but leaves gaps.

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 scrolls within copy mode, a specific action on a specific resource. It also provides details on direction and amount, and mentions it enters copy mode if needed, distinguishing it from related tools like tmux_copy_mode and tmux_copy_search.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only says 'Scroll within copy mode.' Without mentioning when not to use it or suggesting alternatives, the agent lacks context for decision-making among the many sibling tools.

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