tmux_list_panes

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

With no annotations, the description carries the full burden for behavioral transparency. It states the output (IDs, dimensions, status) but does not disclose whether the operation is read-only, if it requires specific permissions, or if it has side effects. The verb 'list' implies non-mutating, but it is not explicitly stated.

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 exceptionally concise, using two sentences to convey purpose and parameter semantics. Every sentence earns its place, with no redundant or fluff content.

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 simplicity (one optional parameter, an output schema present), the description is largely complete. It covers the main use case and parameter formatting. However, the lack of guidance on alternatives and behavioral safeguards slightly reduces completeness, but not enough to lower it further.

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 schema only provides the type and default for the target parameter, but the description adds meaningful detail with examples ('mysession', 'mysession:0') and behavior when omitted. This fully compensates for the schema's lack of description.

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 list tmux panes with specific attributes (IDs, dimensions, status). This is a specific verb+resource that distinguishes it from sibling tools like tmux_list_sessions and tmux_list_windows.

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 explicitly say when to use this tool versus alternatives. It only explains the optional target parameter and default behavior (listing all panes). No mention of when to prefer this over reading a specific pane or listing windows.

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