adb_qemu_start

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

With no annotations, the description covers key behaviors: KVM acceleration, auto-detection of CPUs and RAM, reserving one core for host, and capping custom values. It does not mention error states or return values, but for a start tool, this is sufficient.

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 three sentences, front-loaded with the main purpose. Each sentence adds meaningful information: purpose, auto-detection details, and custom value behavior. No redundancy.

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 the 9 parameters and no output schema, the description covers the essential aspects: purpose, resource allocation, and custom value limits. It could mention return values or prerequisites, but given the sibling `adb_qemu_setup`, it is reasonably 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%, baseline 3. The description adds value by explaining the auto-detection logic for `memoryMb` and `cpus`, and the default for `adbPort`. This goes beyond the schema's property 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 begins with 'Boot a QEMU virtual machine with KVM hardware acceleration,' providing a specific verb and resource. It clearly distinguishes from siblings like `adb_emulator_start` by specifying QEMU and KVM, and from `adb_qemu_setup` by indicating the start action.

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 the tool (to boot a QEMU VM) and provides guidance on resource allocation with auto-detection and safe limits. While it doesn't explicitly exclude alternatives, the auto-detection and capping offer clear usage context.

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