Launch local program

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

The description adds behavioral context beyond annotations: it mentions that launched programs can be optionally visible, and advises post-launch steps for GUI apps. Annotations show destructiveHint: false and readOnlyHint: false, so the description helps clarify it's a launch action but does not detail side effects like process lifecycle or permissions.

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 a single, front-loaded sentence that immediately conveys the core action and parameters, followed by a practical usage tip. Every part is essential and adds value.

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 complexity (4 params, no output schema, no enum constraints) and zero schema description coverage, the description provides a reasonable overview but lacks detail on return values, error handling, or behavior when executable fails to launch. The follow-up advice for GUI apps is helpful but incomplete for the full parameter set.

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%, meaning none of the four parameters are described in the schema. The description adds value by explaining args and visible broadly, but does not document cwd or executable beyond their schema names. Baseline is 3 due to low coverage, and description partially compensates but not fully.

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 it launches a local executable or script with arguments and optionally controls visibility. It distinguishes from siblings like exec by specifying it launches programs and suggests using list_windows and screenshot afterward for GUI apps.

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 explicitly recommends using list_windows and screenshot after launching GUI applications, giving clear follow-up steps. However, it does not provide guidance on when not to use this tool (e.g., versus exec or other launch mechanisms).

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