Launch Application (i3 exec)

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

Annotations already mark as destructive and open-world. Description adds important context: 'runs an arbitrary command line on the user's machine with their privileges — never pass untrusted input.' Also explains behavior of no_startup_id flag.

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?

Three sentences with no redundancy: purpose, warning, and usage guidance for parameter and siblings. Every sentence 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?

Covers all needed context given annotations (destructive, open-world), schema (100% coverage, 2 parameters), and existence of output schema. Includes security warning and sibling differentiation.

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. Description adds practical guidance for no_startup_id: 'Set for programs without startup-notification support (avoids a lingering busy cursor).' This adds value beyond schema.

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 clearly states 'Launch an external program via i3's exec' with specific verb and resource, and explicitly distinguishes from sibling tools like focus_window, move_window, set_layout.

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?

Explicitly states when to use (launching external programs), when not to use (for built-in i3 verbs), and provides security warning about untrusted input. Explains no_startup_id flag usage.

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