adb_multi_shell

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

Discloses parallel execution and grouped results, but with no annotations, fails to mention error handling, partial failure, timeout behavior (though timeout parameter present), or privilege level. More detail would help agents anticipate behavior.

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?

Single sentence, efficient and front-loaded with key action and scope. No unnecessary words.

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?

Lacks output schema and does not detail return structure beyond 'grouped by device'. Missing common pitfalls like device offline or command failure. Adequate for simple use but incomplete for complex scenarios.

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% with clear parameter descriptions. The description adds no new meaning beyond restating the parameter purposes, so it meets baseline but does not enhance understanding.

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 clearly states verb 'execute', resource 'multiple devices', and action 'in parallel', with output grouping. It distinguishes from sibling tools like adb_shell (single device) and adb_root_shell (privileged).

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?

Implicitly suggests use for multi-device shell commands, but does not explicitly exclude single-device use or mention alternatives like adb_shell. The context of sibling tools may help, but the description itself lacks explicit when-to-use vs alternatives.

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