adb_at_batch

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

No annotations are present, so the description must cover behavior. It states 'requires root' and sequential execution, but does not disclose risks like potential device impact, response format, or error handling. The existence of a 'force' parameter hints at danger but is not explained.

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 succinct sentences stating the core action and a key prerequisite (root). No filler, front-loaded.

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?

Despite parameter richness and no output schema, the description lacks details on return format, error behavior, or step-by-step usage. A diagnostic tool would benefit from more context on expected outcomes or failure 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?

With 100% schema coverage, the baseline is 3. The description adds no additional parameter meaning beyond the schema descriptors. No extra context on parameter interactions or usage tips.

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?

The description clearly states the tool sends multiple AT commands sequentially and captures responses. The phrase 'Useful for running a diagnostic sequence' provides context and differentiates it from single-command siblings like adb_at_send.

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?

The description mentions it's useful for diagnostic sequences and requires root, giving clear context. However, it does not explicitly exclude single-command use or mention alternatives, though the batch nature implies when to use.

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