kitty_detach_window

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

No annotations are provided, so the description carries the full burden. It explains default behavior and the effects of target_tab and stay_in_tab. It does not disclose any side effects, failure conditions, or permission requirements, but it provides adequate transparency for a simple move operation.

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 sentences, zero fluff. The first sentence states the core purpose, the second adds key behavioral details. Every word serves a purpose.

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?

Four parameters, none required, no output schema, no annotations. The description covers the main behavior and two key parameters (target_tab, stay_in_tab). The 'self' and 'match' parameters are left to the schema, which is acceptable given high schema coverage.

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 coverage is 100%, so baseline is 3. The description adds value by clarifying the default for target_tab (omitted = new OS window) and the purpose of stay_in_tab (keep focus). This goes beyond the schema's descriptions.

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 action ('Detach windows') and the outcome ('move them to a different tab or a new OS window'). It distinguishes this tool from siblings like kitty_detach_tab and kitty_close_window by specifying moving to tabs or new windows.

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 explains default behavior (new OS window) and how to use target_tab for different destinations. It also mentions the stay_in_tab parameter for focus control. However, it does not explicitly state when not to use this tool or contrast it with similar tools like kitty_close_window.

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