adb_shell_exec

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions the combined write-delay-read behavior but does not explain the effect of the clear flag, default delay, or how errors (e.g., closed session) are handled. The description is adequate but not comprehensive.

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?

The description is a single sentence that efficiently communicates the core behavior. It is front-loaded and free of fluff, though it could include brief notes on prerequisites (e.g., session must be open) without losing conciseness.

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?

The tool lacks an output schema, and the description does not specify the format or content of the output (e.g., stdout, stderr, exit code). It also omits potential issues like timeouts or session expiration. For a tool that retrieves output, this is a significant 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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds no additional semantics beyond the schema; it does not explain defaults (clear=1, delay=1000) or provide usage examples. It meets the baseline but offers no extra value.

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 a command to an ADB shell session and waits for output. It distinguishes from siblings like adb_shell_write and adb_shell_read by explicitly noting it combines write, delay, and read into one call.

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 implies usage for one-step command execution with output retrieval, contrasting with separate write/read calls. However, it does not explicitly state when not to use it or mention alternative tools for streaming scenarios.

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