adb_qemu_connect

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

No annotations provided, so description carries full burden. It discloses prerequisites and localhost restriction, but does not mention return values, error behavior (e.g., what happens if VM not found or timeout), or potential side effects. Still, the key behavioral traits are covered.

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 sentences, each serving a purpose: purpose, prerequisites, and restriction. No redundant or extraneous information. Front-loaded with the action.

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 simple tool (2 parameters, no output schema), the description fully covers purpose, prerequisites, and restrictions. Sibling tools like adb_connect and adb_qemu_disconnect provide necessary context. No gaps for effective use.

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 baseline is 3. The description adds little beyond what the schema provides: it mentions that 'name' must be a running VM and that 'timeout' has a default, but does not add new meaning or format details.

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 'Connect to a running QEMU VM's ADB service' with a specific verb and resource. It distinguishes from sibling tools like adb_connect (remote connections) by explicitly restricting to localhost only, and it explains the effect on DeepADB tools.

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 explicit prerequisites: guest OS must have ADB daemon running (e.g., Android with USB debugging), and requires 'adb' binary with install command. Also states when NOT to use (no remote host connections), implicitly differentiating from adb_connect.

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