execute_shell_command

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

With no annotations, the description must convey behavioral traits, but it only mentions 'full access' without elaborating on potential side effects, output handling, or safety considerations. Running arbitrary commands can modify device state, yet the description does not warn about this or describe what the caller should expect.

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 two focused sentences, front-loaded with the core action and immediately clarifying the tool's arbitrary scope. It is concise with no redundant wording.

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?

This tool executes arbitrary shell commands, which is complex and can have broad effects, yet the description omits return values (e.g., stdout/stderr), error behavior, and potential risks. Without an output schema, the agent lacks crucial information to handle the tool's results safely and effectively.

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 description coverage is 100%, so the baseline is 3. The description adds little beyond the schema: it provides example command strings but does not explain the serial parameter or any additional details about command formatting or execution context.

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 executes an arbitrary shell command on the connected Android device, using a specific verb and resource. This distinguishes it from sibling tools like tap_screen or execute_raw_adb, and the examples (e.g., 'input keyevent 26') illustrate the scope effectively.

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 phrase 'arbitrary shell command' implies this is a general-purpose tool for shell operations not covered by dedicated siblings, but no explicit when-to-use or alternatives are mentioned. There is no guidance on preferring more specific tools when available, leaving usage to be inferred.

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