adb_qemu_start

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

With no annotations provided, the description carries the full burden. It discloses auto-detection logic, resource capping, and host starvation prevention. However, it does not mention behavior when KVM is unavailable, side effects like file creation, or that the VM runs in background and can be stopped via adb_qemu_stop.

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 action and key details. Every sentence adds information without redundancy, making it efficient and easy to parse.

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 tool's complexity (9 parameters, 2 required, no output schema), the description covers the core functionality, resource allocation strategy, and custom value handling. It lacks details on return values or failure modes, but for a start tool the coverage is sufficient for an agent to use it correctly.

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 description coverage is 100%, and the description adds value beyond schema by explaining the auto-detection rationale and capping behavior. For example, 'memoryMb' schema says 'Auto-detected if omitted (65% of physical RAM)' but the description gives the reasoning behind the 65% and capping.

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 'Boot a QEMU virtual machine with KVM hardware acceleration' with a specific verb and resource. Among sibling tools, it differentiates itself by emphasizing KVM acceleration and auto-detection of resources, distinguishing it from other emulation tools like adb_emulator_start.

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 provides explicit guidance on when to use default vs. custom resource values: 'Auto-detects optimal resource allocation... Custom values are accepted but capped at safe limits to prevent host starvation.' It gives context for usage but does not directly compare to alternative tools like adb_emulator_start.

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