adb_qemu_guest_shell

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

No annotations provided. Description adds internal detail (guest serial derived internally, no external host/IP) and compares behavior to adb_shell. However, does not mention return values, side effects, or failure modes.

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 focused sentences covering purpose, prerequisite/internal behavior, and security. No redundant or extraneous content.

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?

Covers prerequisite and security context. For a command execution tool with schema-documented parameters, it is mostly complete. Could be improved by specifying return value format or error handling.

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%. Description adds no extra parameter detail beyond what schema already provides. Baseline score of 3 is appropriate.

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 'Execute a shell command on a QEMU guest VM via ADB', specifying verb, resource, and context. Differentiates from adb_shell by targeting QEMU guests.

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?

Explicitly states prerequisite: VM must be connected via adb_qemu_connect. Notes security middleware checks similar to adb_shell, but lacks explicit when-not-to-use or alternative tools.

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