Run arbitrary tmux command

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

No annotations are present, so the description must convey behavioral traits. It discloses that arguments are passed 'raw' (no preprocessing) and warns that the user is responsible for correctness and safety, implying lack of built-in safety checks. However, it does not detail output behavior or specific side effects, which is a modest gap for a potentially dangerous arbitrary-execution 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?

Two concise sentences with no filler. Front-loaded with the tool's core action, followed by usage guidance and a safety warning. Every word earns its place.

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 simple passthrough nature and full schema coverage, the description is largely complete: it states purpose, when to use it, and the user's responsibility. It could benefit from a brief example or note about return values, but these are not critical for a raw exec command.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds minimal extra meaning beyond the schema, mainly reinforcing that args are 'raw' (passed as-is). It does not elaborate on the 'confirm' or 'host' parameters, but the schema already documents them sufficiently.

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 identifies the tool as executing any tmux subcommand with raw arguments, using the specific verb 'execute' and the resource 'any tmux subcommand'. This distinguishes it from the many focused sibling helpers, making its purpose unambiguous.

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 explicitly states 'Use this when helpers do not cover your use case', providing a clear context for when to choose this tool over specialized helpers. While it doesn't name specific alternatives, the general rule is clear and actionable.

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