tmux_respawn_window

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

No annotations provided, so description fully bears responsibility. It discloses default behavior, force-kill option, command default, directory setting, environment injection behavior (with tmux version note), and return format. Comprehensive disclosure.

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?

Highly concise with no wasted words. Front-loaded with purpose, then parameter details. Structured logically from default behavior to overrides.

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 6 parameters, 1 required, and no output schema, description covers behavior, parameters, return value, and version constraints. Missing 'target' parameter and could clarify return format with more detail, but overall sufficient.

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%, so description must compensate. It explains 5 of 6 parameters (window implied, command, kill, start_directory, env) but misses 'target'. Adds significant meaning beyond schema defaults.

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?

Description uses specific verb 'Restart the command' and resource 'window (respawn-window)', and clearly distinguishes from sibling 'tmux_respawn_pane' by noting it applies to the whole window (single/first pane).

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?

Provides clear context: default behavior only for exited commands, force restart with kill=True, defaults for command and start_directory, and environment handling caveat. However, does not explicitly compare to alternatives or provide when-not-to-use guidance.

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