adb_qemu_connect

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

Discloses requirements and localhost restriction, but does not mention potential blocking behavior or side effects on failure. Without annotations, description carries full burden; it covers key safety info but leaves behavioral gaps like timeout handling.

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 concise sentences with no redundancy. Front-loaded with purpose, followed by prerequisites and a critical restriction. Every sentence adds value.

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 no output schema and 2 parameters, description covers prerequisites and restrictions adequately. Lacks mention of output format or post-connection state (e.g., need to disconnect), but context of sibling disconnect tool mitigates. Complete enough for a connection tool.

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 covers both parameters fully (100% coverage). Description adds marginal value by restating default and range for timeout, but no extra meaning beyond schema. Baseline at 3.

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?

Clearly states verb (connect), resource (QEMU VM's ADB service), and effect (guest appears as device). Distinguishes from general ADB connect by specifying QEMU VM context, but could explicitly differentiate from adb_connect for physical devices.

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 prerequisites (ADB daemon running, adb binary) and a restriction (localhost only). Lacks explicit when-to-use vs alternatives, but context implies exclusive use for QEMU VMs.

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