android_emulator_start

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

With no annotations, the description must convey behavior. It does so by explaining that it blocks until boot is complete, and the parameters 'wait' and 'timeout' clarify the waiting behavior. It does not mention side effects like resource consumption or failure handling, but the essential behavior is disclosed.

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 extremely concise: a single sentence stating the purpose, followed by a clean, bulleted list of parameters with one-line explanations. Every word earns its place, and the key action is front-loaded.

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 tool that boots an emulator, the description covers the main behavior (boot and wait), the parameters, and even references a related sibling for listing AVDs. It lacks explicit failure behavior or what happens if the AVD doesn't exist, but given no output schema and the simplicity of the action, it is adequately 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?

The schema only provides parameter names and defaults, so the description's Args section adds crucial meaning: 'avd' is described as a name from android_devices, 'wait' blocks on sys.boot_completed, and 'timeout' sets the maximum wait. This compensates well for the lack of schema descriptions.

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 ('Boot') and the resource ('emulator AVD'), and explains the core behavior of waiting until ready. This distinguishes it from sibling tools like android_screenshot or android_tap, which operate on a running emulator rather than launching one.

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 usage for starting an emulator, and the reference to 'android_devices' for the AVD name provides context. However, it does not explicitly state when to prefer this over alternatives, such as when an emulator is already running or if you just need to check device status.

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