Snapshot tmux state (readonly)

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

No annotations are provided, so the description carries the full burden. It explicitly states 'readonly' and 'without modifying defaults', which are key behavioral disclosures. However, it does not mention potential side effects like network access or the semantics of 'recent capture', leaving some 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 a single sentence that front-loads the tool's purpose and key differentiator. It avoids redundancy and every word contributes to understanding the tool's function.

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?

While the description lists what the tool retrieves, it does not explain the output format or define 'recent capture', which is important since there is no output schema. The parameter schema covers inputs, but the description could provide more context about expected return data or usage scenarios.

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 100% schema description coverage, the parameters are already well-documented. The description adds only a loose link to 'recent capture' (likely the captureLines parameter) but does not provide additional detail about how host, session, or captureLines interact beyond what the schema states.

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 states a specific verb ('retrieve') and resource ('sessions, windows, panes, and recent capture'), and explicitly distinguishes itself as a 'readonly variant of tmux_state'. This clearly sets it apart from the sibling tool tmux_state and other manipulation tools.

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?

It communicates when to use this tool: when a read-only snapshot is needed and defaults should not be modified. It names the alternative 'tmux_state' but does not provide explicit 'when-not' conditions or mention other alternatives like tmux_list_* or tmux_capture_pane.

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