adb_qemu_guest_shell

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

No annotations provided, so description carries full burden. It discloses internal guest serial derivation and security middleware checks, but omits output format (stdout/stderr), timeout behavior, and error handling. Covers core behavior but not edge cases.

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: action, prerequisite+internal detail, security note. No fluff, though could be more structured (e.g., bullet points) for scanning.

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 similarity, but missing output format, error handling, and timeout details. Adequate but not fully self-contained for a no-annotations 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 coverage is 100%, so description adds minimal extra value. It does add context for the 'name' parameter (prerequisite for connection) but does not elaborate beyond schema descriptions.

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?

Description states 'Execute a shell command on a QEMU guest VM via ADB', which is a specific verb-resource pair. The tool name and context clearly distinguish it from adb_shell (standard ADB shell). However, it does not explicitly compare to siblings.

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?

Description mentions prerequisite 'VM must be connected first (use adb_qemu_connect)' and compares security to adb_shell. It lacks explicit when-to-use vs. alternatives like adb_shell or adb_qemu_start, so guidance is adequate but not comprehensive.

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