mobile_launch_app

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

With no annotations provided, the description carries full burden. It only states 'Launch an app' and that it returns a JSON response, without disclosing side effects, prerequisites (e.g., app installed), failure modes, or whether it blocks. This is minimal disclosure for an action that mutates device state.

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 highly concise: one sentence for purpose, a clean argument list, and a returns line. Every part is useful and front-loaded, with no redundant phrasing.

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?

The tool is simple, but the description omits important context: error handling (e.g., if app not installed), whether it waits for launch completion, and prerequisites like device connectivity. The output schema exists but is not described in detail. Overall, it covers the basics but leaves gaps an agent might need.

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?

Despite 0% schema description coverage, the description compensates well: it explains serialno is the device ID from list_devices, and app_name is a package name or bundle ID per platform. This adds meaning beyond the bare parameter names in the schema, though it lacks examples or format validation.

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 states a specific verb ('Launch') and resource ('an app') on a device. It is unambiguous and distinguishes from sibling tools like mobile_stop_app or mobile_current_app by the core action. The parameter names are also clarified, making the purpose crystal clear.

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 some context (serialno from list_devices, app_name format) but does not explicitly state when to use this tool vs alternatives like mobile_stop_app or mobile_current_app. There are no exclusions or conditions. The usage is implied by the action, but the guidance is not explicit.

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