tmux_capture_pane

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

Annotations give readOnlyHint=true, and the description reinforces read-only behavior. It details special behaviors: start/end line range handling, escapes, join, trim, and the return format. No contradictions. The description adds value beyond annotations by explaining these nuances.

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 four sentences long, front-loaded with purpose, and each sentence provides essential detail without redundancy. It efficiently conveys the tool's function, parameters, and return value.

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 complexity (7 parameters, no output schema), the description covers the return value and explains most parameters. The two unmentioned parameters (target_pane, target) are common in tmux tools and may be inferred, but their omission is a minor gap. Overall complete for the task.

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 explain parameters. It thoroughly explains start, end, escapes, join, and trim. However, it omits explanations for target_pane and target, which are two of seven parameters. Despite this, the most critical parameters are well described.

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 'Capture (read) the visible contents and/or scrollback of a pane' with a specific verb and resource. It distinguishes itself as 'the primary way to observe output', differentiating from sibling tools like tmux_command or tmux_send_keys which write or execute commands.

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 clear context: 'This is the primary way to observe output.' It implies use for reading pane content. However, it does not explicitly state when not to use it or mention alternative tools for similar tasks, but the context is sufficient.

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