adb_multi_test

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

Discloses parallel execution, per-check comparison, and profile details. However, without annotations, it omits potential side effects, permission requirements, or output format. Some behavioral traits (e.g., max custom commands) are mentioned.

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 sentences: first states main purpose, second enumerates profiles and custom commands. No filler, every sentence adds value. Front-loaded with key action.

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 tool purpose, parameters, and basic execution model. Lacks output details (format of matches/differences) and any error handling or prerequisites. Adequate but not fully comprehensive for a complex multi-device 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%, but description adds value by explaining profile meanings (e.g., 'firmware' includes baseband, bootloader) and noting 'full' runs all. This goes beyond the enum 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 clearly states it runs a comparative test workflow across all connected devices, listing specific profiles and custom commands. It distinguishes from siblings like adb_multi_compare and adb_multi_shell by focusing on comparative testing.

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 provides clear context for when to use (comparative testing across devices), but does not explicitly exclude alternatives or mention when not to use. No direct comparison to similar sibling tools.

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