tmux_clear_history

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

The description reveals that only the scrollback buffer is cleared, leaving the visible screen untouched. Annotations indicate destructiveHint=true, and the description confirms this non-destructive effect on visible content and specifies the return value.

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 at three sentences, front-loaded with the core action, and efficiently explains the use case and return value without extraneous words.

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's low complexity and optional parameters, the description covers behavior, use case, and return value. However, the lack of parameter documentation (0% schema coverage) is a missing piece that slightly reduces completeness.

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 compensate. It mentions target_pane only implicitly in the return format and through the tmux command syntax, but does not explain the difference between target_pane and target, their formats, or defaults. This leaves a significant gap.

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 wipes a pane's scrollback history using the tmux command 'clear-history -t pane'. It distinguishes from siblings like tmux_capture_pane and tmux_send_keys by explaining the use case for a clean slate.

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 explicitly recommends using this before tmux_send_keys or tmux_run to ensure a clean capture start. It does not provide explicit when-not-to-use criteria, but the context is clear.

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