tmux_list_sessions

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

No annotations exist, so the description carries the full burden. It implies a read-only operation by stating 'List active tmux sessions', but does not provide details such as the exact output structure, whether it returns session IDs or names, or any potential side effects. The phrase 'created by this server' adds some scope context, but key behavioral aspects remain unspecified.

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, focused sentence that is front-loaded and contains no extraneous information. It perfectly balances brevity with clarity.

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 (no parameters), the description is mostly sufficient. However, the absence of an output schema means the description should have indicated what the response looks like (e.g., session names, IDs, status). Without that, the agent must infer the return format. Also, no guidance on when to use this versus sibling tools reduces completeness.

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 tool has zero parameters, so the schema is trivially covered at 100%. Per the baseline for 0-param tools, a score of 4 is appropriate. The description adds contextual meaning by specifying that only active sessions created by this server are listed, but there are no parameters to describe.

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 identifies the tool as listing active tmux sessions specifically created by this server, using a specific verb ('List') and resource ('tmux sessions'). The qualifier 'created by this server' differentiates it from the sibling 'list_sessions' tool, which likely covers sessions from other sources.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_sessions' or other tmux-related tools. The description only states what it does, without any context on use cases or exclusions.

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