Android boot

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

Annotations indicate a mutating, non-idempotent operation. Description adds that it primes the private frame source used for coordinate mapping, and discloses that MCP has no live DSH sidebar, steering to android_screenshot. This goes beyond annotations by describing side effects and limitation.

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?

Three concise sentences, front-loaded with purpose, then input handling, then limitation/alternative. No filler.

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 single-parameter tool with no output schema, the description covers purpose, input selection, and a key limitation (no live sidebar). It implies its role in coordinate mapping but does not explicitly state that it must be called before interaction tools, which would be helpful. Otherwise it's fairly 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% and the schema description already explains serial vs AVD and boot behavior. The tool description echoes this but adds no new semantic detail for the parameter. Baseline 3 is appropriate.

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?

States a specific verb ('Prepare') and resource ('an Android target'), and notes the launch/boot behavior. It distinguishes itself from android_screenshot by pointing out that it primes the frame source, so an agent can see it's not just for viewing.

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?

Provides context that the device can be a serial or AVD, and that an AVD is booted. Recommends android_screenshot for seeing the device, but does not explicitly compare to interaction tools like android_tap_element or android_launch_app. The guidance is mostly about the input and viewing, not about sequencing relative to other boot tools.

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