tmux_kill_pane

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

The description labels the tool as 'destructive', which matches the annotation destructiveHint=true but adds no new behavioral context beyond what annotations already provide. No additional details on side effects or permission requirements.

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 very short (one sentence) with no wasted words, but it is too terse and omits essential information. Conciseness is not improved by lack of substance.

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 and the absence of output schema, the description should at least explain the effect and parameters. It fails to provide adequate context for proper 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?

Schema description coverage is 0%, and the description provides no explanation of the parameters (target_pane, target). It does not clarify their format, meaning, or how to specify a pane.

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 the verb 'Kill' and resource 'pane', distinguishing it from other kill tools (tmux_kill_session, etc.). However, it lacks specifics on what happens (e.g., removing the pane or terminating the process), making it less informative than a high-quality description.

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 like tmux_break_pane or tmux_kill_window. The description does not mention prerequisites or usage context.

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