tmux_list_sessions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not clarify the output format, error behavior (e.g., no sessions), or any side effects. It adds minimal context beyond the purpose itself, matching the baseline for a simple read tool.

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, clear sentence with no unnecessary words. It is appropriately sized for a tool with no parameters and a simple purpose.

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 zero-parameter list operation, the description is succinct but incomplete in context. It does not mention what the output looks like (since there is no output schema), nor does it note how to handle or interpret the results. This is a moderate gap, though the tool's simplicity mitigates the issue.

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 has zero parameters, so description coverage is 100% and the baseline is 4. No parameter explanation is needed, and the description does not add any parameter-related details because there are none.

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 'List all tmux sessions' uses a specific verb ('list') and resource ('tmux sessions'), clearly distinguishing it from sibling tools like tmux_list_windows and tmux_list_panes. It is unambiguous and precisely states the tool's function.

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 state when to use this tool versus alternatives, though the distinction is implied by the resource name. There is no exclusion guidance, such as 'for windows/panes, use tmux_list_windows/list_panes'. Context is clear but no alternatives or exclusions are mentioned.

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