tmux_version

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

The description adds beyond the readOnlyHint annotation by specifying what is reported: the version string and a supported flag (1.8+). This is useful context. No contradictions with annotations.

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, efficient sentence that conveys the core functionality with no unnecessary words. It is ideally concise.

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 (one optional parameter, read-only, no output schema), the description is mostly adequate. However, the lack of parameter definition leaves a gap that could cause incorrect usage.

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 0% description coverage, and the tool description does not explain the 'target' parameter. The word 'target' appears only in the purpose statement without clarifying its meaning, format, or allowed values. This is a significant gap.

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 reports the target's tmux version and whether it is supported (1.8+). It uses a specific verb and resource, distinguishing it from other tmux tools that perform different actions. However, it does not explicitly differentiate from siblings like tmux_server_info, which might also provide version info.

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. For example, it does not explain when to use tmux_version instead of tmux_server_info or tmux_list_sessions. There is no mention of prerequisites or context.

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