Build, install and run

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

No annotations are provided, so the description carries the burden. It discloses the installation mechanism (adb install -r), which implies data preservation, and states the need for appId. However, it does not mention potential wait times, required device/emulator connectivity, or the fact that this is a potentially long-running Gradle operation. Some behavioral light is shed, but gaps remain.

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 two sentences long, with the action verb 'Build' leading. It packs essential details (adb install -r, appId requirement) without fluff. Every word contributes. Front-loaded and efficiently structured.

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 composite tool with five optional parameters, the description covers the main workflow and a key prerequisite (appId). No output schema exists, so the description does not need to explain return values ambiguously. It could mention that it's a potentially long-running Gradle build and requires a connected device, but the core flow is clear. Slight room for more context, but largely complete.

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%, so parameter semantics are already fully documented. The description adds a note that appId defaults to session, which is already in the schema ('defaults to session'). No additional parameter meaning is provided beyond schema hints. Baseline 3 is appropriate when the schema covers everything.

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 a compound action: 'Build the APK, install it on a device/emulator (adb install -r), and launch the app.' This distinguishes it from siblings like build_app, install_app, and launch_app by covering all three steps. The specific verb+resource combination makes the purpose unmistakable.

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 implies when to use it: when you need the full build-install-launch pipeline. It also notes the appId requirement, which is a prerequisite. However, it does not explicitly mention alternatives or exclusions, such as using build_app alone if you only want to compile. Clear context but no direct comparison to sibling tools.

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