launch_simulator

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

No annotations, so the description carries the full burden; it does disclose the important blocking trait — it waits for TCP port 1234 to open rather than returning immediately. It omits key behaviors: what happens on timeout (error vs. silent return), whether it fails or is a no-op if a simulator is already running, and whether the launched app persists after the call.

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?

One tightly written sentence that front-loads the action and appends the observable completion condition. No filler or redundant restatement of the tool name.

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 single-optional-parameter launcher with no output schema, the core action is covered, but timeout behavior and the already-running case are practical concerns an agent needs and neither is stated. Adequate but with clear gaps for a stateful process-launching tool.

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% and the schema already documents wait_ms including the 15000 default and port 1234. The description adds no further semantics such as recommended values or what a too-short wait means for the caller. Baseline 3 applies since the schema does the heavy lifting.

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?

Names a specific verb+resource ('Launch the Garmin Connect IQ simulator application') and specifies the concrete artifact (ConnectIQ.app from the SDK). The verb contrast with siblings terminate_simulator and simulator_status is unambiguous even without naming them.

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?

No explicit when-to-use or when-not-to-use guidance, no prerequisites (e.g. SDK installed, no simulator already running), and no routing to alternatives like terminator/status. The ordering relative to build_app/run_app is left to inference, though the launch semantics make the general intent fairly obvious.

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