Snapshot tmux state

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states the output ('Return sessions, windows, panes, and last lines') and does not disclose whether the operation is read-only, has side effects, or has any limitations. The verb 'Return' implicitly suggests a read operation, but minimal explicit behavioral context is given.

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, well-structured sentence that immediately states what the tool returns. There is no unnecessary information or filler, making it highly concise and front-loaded.

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?

The tool has no output schema, and the description does not explain the structure of the returned data or the effect of the optional parameters. Given the many sibling tools with overlapping functionality, the description lacks contextual guidance to help an agent choose appropriately. It is adequate for the simple read operation but leaves gaps.

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 input schema has 100% coverage with descriptions for all three parameters (host, session, captureLines). The tool description adds no extra semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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 returns a snapshot of tmux state including sessions, windows, panes, and last lines. The verb 'Return' is specific and the resource list is concrete. However, it doesn't explicitly differentiate from sibling tools like tmux_list_sessions or tmux_capture_pane, so it doesn't fully earn a 5.

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 provides no guidance on when to use this tool versus alternatives such as tmux_list_sessions, tmux_capture_pane, or tmux_readonly_state. There is no mention of preferred use cases, exclusions, or alternatives.

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