Run a shell command

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

With no annotations, the description carries the entire behavioral burden, and it discloses almost nothing: no indication that this is arbitrary, potentially destructive code execution, no mention of required device permissions/root, no timeout, no statement about what is returned (stdout/stderr/exit code). For the most powerful tool in the set, this is a substantial gap.

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?

Two short sentences, front-loaded with the core action and followed by the routing hint. No wasted words, though the second sentence is slightly vague where it could be sharper.

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?

No output schema and no annotations, so the description must explain return behavior and safety on its own — and it does neither. An agent cannot tell whether output is captured, whether the call blocks, or what side effects are possible before invoking arbitrary shell commands.

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 50%: `serial` is documented in the schema, while `command` has no description. The phrase "a command in the device shell (adb shell)" partially compensates by implying the string is passed to adb shell, but it adds no detail on quoting, shell interpretation, or multi-command usage.

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 — run a command in the device shell — and names the underlying mechanism (adb shell), so the agent knows exactly what capability this exposes. It does not name a specific sibling it overlaps with, but the catch-all framing makes its role in the 18-tool family clear.

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?

"For anything the other tools do not cover" gives a concrete selection rule: treat this as the fallback when no dedicated phone_* tool fits. It stops short of naming which alternatives exist or stating exclusions/limits on what may be run, so it is context rather than a full routing spec.

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