Launch the app

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

The description discloses all behavioral traits beyond annotations: it launches an app with side effects, returns metrics, conditionally force-stops and wipes data (clean=true), and falls back to monkey. Annotations only provide readOnlyHint=false and destructiveHint=false, but the description clarifies the conditional destructive nature, adding value.

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, well-structured sentence that front-loads the main action and return value, then concisely explains each parameter variant. No redundant or unnecessary words; every sentence adds value.

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 no output schema, the description adequately explains the return value (cold-start metrics). It covers all five parameters and their effects, including conditional behavior, fallback, and device serial. The tool's complexity is fully addressed.

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?

With 100% schema description coverage, the description adds significant context beyond the schema, such as the return of cold-start metrics, the force-stop and wipe behavior for clean=true, the mutual compatibility of deepLink and activity, and the fallback to monkey when resolution fails. This enhances understanding of parameter interactions.

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 tool launches an app via `am start -W`, specifies it returns cold-start metrics, and distinguishes itself from sibling tools (no other launch tool among siblings). The verb 'Launches' and resource 'app' are precise, and the description covers all usage variants.

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 explains when to use each parameter (clean, deepLink, activity, serial) and how they interact. It also describes the automatic resolution fallback. However, it does not explicitly state when not to use this tool or provide explicit alternatives, though none exist among siblings.

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