adb_shell_exec

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only mentions waiting for output and combining write+delay+read. It does not disclose timeout behavior, buffer clearing semantics, or side effects of long-running commands, which are partially captured in the schema but not in the description.

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 extremely concise, with two short sentences that immediately convey the core purpose and behavior. Every word earns its place, and there is no redundant filler.

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 has 5 parameters with complex semantics (e.g., maxDuration overrides depending on command type) and no output schema, but the description does not explain return values, timeout actions, or the relationship between session_id and adb_shell_open. The description is too thin to fully prepare an agent to invoke the tool correctly in all 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?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds no additional parameter-level meaning beyond what the schema provides, such as the significance of 'clear' or 'maxDuration'.

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, using a specific verb and resource. It explicitly notes that it combines write, delay, and read, which differentiates it from sibling tools like adb_shell_write and adb_shell_read.

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 by stating it combines write, delay, and read, but it does not explicitly state when to use this tool versus alternatives such as adb_shell_write, adb_shell_read, or adb_exec. There is no exclusion or comparison guidance, leaving the agent to infer the appropriate context.

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