Close i3 Window

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

Beyond annotations (destructiveHint=true), the description details that the target application is asked to quit, unsaved work may be discarded, no undo, and matching several windows closes all. This adds significant context.

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: first states purpose, second provides behavioral warning and alternative. Every sentence earns its place, no redundancy.

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 tool with 5 optional criteria parameters, destructive behavior, and an output schema (not shown but indicated), the description covers purpose, criteria, destructive consequences, and alternative usage. No gaps.

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. However, the description adds value by listing the criteria types (class, title, instance, mark, con_id) and implying they are for matching, which reinforces and slightly expands on the schema 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 explicitly states 'Close a window — the focused one, or one matched by class/title/instance/mark/con_id'. It uses a specific verb ('Close') and resource ('window'), and distinguishes from sibling `move_window` by mentioning the destructive nature and alternative.

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 provides clear guidance: use to close windows, not to move them out of the way (referencing `move_window`). It also warns about destructiveness and multiple windows matching.

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