ios_launch_app

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description doesn't need to restate that. It adds that launching brings the app to foreground and returns a screen, but doesn't disclose side effects around app restart behavior, waiting, or error cases if the app isn't installed.

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 with no filler: it names the action, the object, and the result. Every word contributes to the agent's understanding.

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 simple two-parameter tool with a complete input schema, annotations, and an output schema, the description is mostly sufficient. The only notable gap is the lack of behavior on failure (e.g., missing bundle_id app) and how it interacts with currently running apps, but these are minor given the schema and output schema coverage.

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 100%, with both bundle_id and fresh documented. The description adds no parameter-level detail beyond what the schema already provides, so the baseline score of 3 applies.

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 action ('Bring an app to the foreground') and the expected outcome ('return its screen'), and the tool name reinforces this. It distinguishes itself from siblings like ios_terminate_app and ios_install_app, though it doesn't explicitly distinguish 'return its screen' from ios_screenshot.

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 gives no guidance on when to use this tool versus alternatives such as ios_open_url, ios_install_app, or ios_screenshot. There are no exclusions, prerequisites, or context hints beyond restating the action itself.

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