Toggle synchronize-panes

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

With no annotations, the description carries full burden. It only restates the name and function without disclosing behavioral implications, such as that synchronize-panes affects all panes in the target window, whether the change is persistent, or if any permissions are required. This lacks depth for a mutation tool.

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, concise sentence with no redundant wording. It is efficiently front-loaded with the core action. It loses one point for being so minimal that it borders on under-specification, but overall it is appropriately sized.

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 setter with fully described parameters and no output schema, the description is minimally viable. It conveys the essential purpose but omits behavioral context such as the effect on all panes. This is sufficient for a straightforward toggle, hence a score of 3.

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 100%, so the baseline is 3. The description does not add any parameter meanings beyond what the schema already provides. The schema adequately explains 'on' and 'target', so no additional clarification is needed.

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 specific action: 'Enable or disable synchronize-panes for a window.' It identifies the verb (enable/disable), the resource (synchronize-panes), and the scope (a window). This is unambiguous and distinguishes it from sibling tools that handle other tmux settings.

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. It does not mention any exclusions or prerequisites beyond what the schema implies. The tool's purpose is clear, but there is no explicit usage context, which earns a score of 2.

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