adb_qemu_setup

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

With no annotations, the description must cover behavioral traits. It describes checks (KVM, version) and install via Termux, but doesn't disclose potential side effects (e.g., network usage, storage impact) or behavior when KVM is unavailable. It is adequate but could be more transparent.

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 concise sentences with no fluff. Each sentence adds essential information: purpose, actions, and constraint. Excellent front-loading of the purpose.

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 simplicity (one boolean parameter, no output schema), the description covers the main functionality: checking and installing QEMU, with the constraint of on-device mode. It doesn't mention return values or what happens when install=false, but these are minor omissions.

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 the description's explanation of the 'install' parameter ('if true, install QEMU via pkg if not already present') largely mirrors the schema. No additional semantics are provided beyond what the schema already conveys.

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 it checks and installs QEMU for on-device virtualization, with specific actions: verifying KVM, checking installation, reporting version, and optional install. It distinguishes itself from sibling tools like adb_qemu_connect and adb_qemu_start which deal with running QEMU.

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?

It mentions the tool is only available in on-device mode, which is a key constraint. While it doesn't explicitly compare to alternatives, the context of sibling tools implies this is the setup tool before using other QEMU commands. Slightly more explicit guidance would improve clarity.

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