tmux_list_panes

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

Annotations confirm readOnlyHint: true, and the description adds scoping behavior (window, session, all). However, it does not disclose return format, ordering, or any potential side effects, leaving some behavioral gaps.

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 extremely concise: two short sentences front-loading the main action and scoping options. Every word is informative, with no redundancy or unnecessary detail.

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?

For a simple listing tool with readOnlyHint and no output schema, the description is mostly adequate but incomplete regarding the 'target' parameter and output format. It covers the core scoping but misses some details.

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?

With 0% schema coverage, the description adds meaning for 'window' and 'session' parameters by mapping to tmux flags (-t, -s). However, it does not explain the 'target' parameter from the schema, leaving one parameter undocumented.

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 'List panes' with a specific verb and resource, and distinguishes from sibling tools like tmux_list_windows and tmux_list_sessions by explicitly mentioning scoping options.

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 explains when to use each parameter: window (-t), session (-s), or whole server (default -a), providing clear context for usage. However, it doesn't explicitly mention alternatives for other listing tasks, though the tool name and siblings make it implicit.

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