adb_command

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

No annotations are supplied, so the description carries the full burden. It usefully discloses mode routing, the 20s default timeout, and multi-device targeting, but says nothing about the risk profile of arbitrary command execution (installs, keyevents, process kills), permission/prerequisite requirements, or what happens on timeout.

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?

Front-loaded one-line summary followed by an args list that is easy to scan, with no filler. The Args formatting is somewhat verbose relative to the content but every entry adds usable detail.

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?

An output schema exists, so return values needn't be explained, and all parameters plus both execution modes are covered. Given this is an unrestricted command-execution tool with no annotations, the missing risk and prerequisite context is the main gap.

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 description coverage is 0%, yet the description documents all four parameters with concrete example values and clarifies that device_serial should be sourced from adb_list_devices. It stops short of describing timeout-expiry behavior or output capture for the command itself.

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?

States a specific verb and resource: execute an ADB shell command or host ADB operation on a connected device. It also disambiguates from the sibling adb_list_devices by explaining where device_serial comes from, so an agent can place it among the adb/serial/toolchain 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?

Gives clear selection logic between the two modes: is_shell=True runs `adb shell <command>` and False runs `adb <command>`, each with concrete example commands. It explains when device_serial matters (multiple devices connected) but offers no when-not guidance or explicit alternatives among siblings.

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