ios.launch_app

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

With no annotations provided, the description carries the burden. It discloses approval requirements, device mutation, and danger via tags, which are important behavioral traits. It does not detail failure modes or side effects beyond those tags, but the explicit risk markers are valuable.

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 sentence with front-loaded tags, which is efficient and direct. Every word contributes to the core purpose, though it is minimal and could include more detail without becoming verbose.

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 three parameters, no output schema, and no annotations, the description is insufficient. It does not explain device selection, terminateRunning behavior, or what happens on launch (e.g., success/failure semantics). An agent would need to infer these from the schema alone.

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%, so the description must explain parameters. It only clarifies that bundleId is used for launching ('by bundle id') but provides no guidance on the device parameter or terminateRunning. This leaves two of three parameters unexplained.

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 the verb (Launch), the resource (installed iOS simulator app), and the method (by bundle id). It distinguishes from sibling tools like ios.install_app (installing) and ios.boot_simulator (booting) by focusing on launching an already-installed app.

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 phrase 'installed' implies a prerequisite—that the app must be installed first, hinting at using ios.install_app before this. It does not explicitly name alternatives or exclusions, but the context is clear for a launch operation.

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