launch_on_headless_desktop

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

The description adds significant behavioral context beyond annotations: it creates the desktop if needed, runs a full GUI on the hidden desktop, and never touches the visible desktop. This aligns with the destructiveHint annotation and provides valuable transparency.

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 concise with two paragraphs and an args/returns section. Every sentence adds value, and the main action is front-loaded. No redundant or filler content.

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 simplicity (two parameters, clear behavior) and the presence of an output schema (implied by return format), the description is complete. It explains the launch process and subsequent operations, covering all necessary guidance.

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?

The description mentions 'desktop name and command line' for parameters, but the input schema already provides similar minimal descriptions. The description does not add extra meaning beyond what the schema provides, so it meets the baseline expectation.

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 GUI application on an off-screen desktop, creating the desktop if needed. It uses specific verbs and resources, distinguishing it from siblings like launch_on_virtual_display and close_headless_desktop.

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 guidance on using list_headless_windows to find windows and driving them with background input and screenshots. It states the visible desktop is never touched, giving clear context. However, it does not explicitly list when not to use or mention alternatives.

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