tmux_list_windows

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys a read-only list operation with optional filtering, but does not state side effects, output format nuances (though an output schema exists), or error behavior. It is non-misleading, and the list verb implies safety, but additional context would improve transparency.

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 concise and front-loaded: the first sentence states the core action, the second explains the optional filter, and the Args section is clear and minimal. No wasteful sentences.

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 list tool with one optional parameter and an output schema, the description covers the essential usage and behavior. It is sufficiently complete given the tool's complexity and the structured schema.

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?

Schema description coverage is 0%, but the description fully explains the only parameter 'session' — its meaning (name or ID) and effect (filter by session, or list all if omitted). This adds significant value beyond the raw schema type string|null.

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 'List all tmux windows' with an optional filter, using a specific verb ('List') and resource ('tmux windows'). It distinguishes from sibling tools like tmux_list_panes and tmux_list_sessions by naming the resource directly.

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 indicates when to use the tool (list windows, optionally for a specific session) and explains the behavior when the optional filter is omitted. However, it does not explicitly contrast with alternatives like tmux_list_panes, though the resource name makes the distinction obvious.

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