Capture multiple panes (batch)

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

The description provides two important behavioral traits: 'readonly' and 'parallel'. These add value, especially since no annotations are provided. However, it does not disclose potential caveats such as partial failure behavior, output format, or whether there are limits on concurrency. The readonly hint is strong, but the description remains thin on other execution characteristics.

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 a single, concise sentence that front-loads the essential action and scope. It avoids unnecessary detail and is easy to parse, making it highly efficient for an agent.

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 tool has a moderately complex input schema (array of objects) and no output schema. The description does not explain the return format, how errors are handled, or any prerequisites. Given the batch nature and complexity, the description is insufficient for an agent to fully understand the tool's behavior without additional inference.

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 does not explain any parameters. While the schema includes some descriptions for nested properties and defaultLines, the top-level 'targets' parameter and 'defaultLines' are not described in the tool description. With schema description coverage at 50%, the description should compensate, but it adds no parameter guidance beyond the general idea of 'multiple panes'.

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: to capture scrollback from multiple panes in parallel. The verb 'capture' and specific resource 'scrollback from multiple panes' differentiate it from sibling tools like tmux_capture_pane (which captures a single pane) and tmux_tail_pane (which tails output). The addition of 'parallel' further clarifies its batch nature.

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 implies usage for capturing scrollback from multiple panes simultaneously, which gives clear context for when to use this tool. However, it does not explicitly name alternatives or state when not to use it. Since it says 'multiple panes', it is clear this is meant for batch scenarios, which is distinct from single-pane capture.

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