run_android_cli

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

With no annotations provided, the description carries the transparency burden. It states that stdout is returned and that the Android CLI must be installed, which is useful. Yet it omits behavior on stderr, exit codes, or error handling, leaving potential ambiguity for a command executor.

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 concise and front-loaded, with the action in the first sentence. The subsequent list of subcommands is dense but directly relevant, and the prerequisite is stated in one short clause. No waste.

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?

Given the tool's simplicity and rich schema (cwd and command with examples), the description covers the main aspects: what it does, when to use it, and a requirement. It could also mention handling of non-zero exits or stderr, but this is likely not critical for correct selection and invocation.

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%, and the schema includes descriptive examples. The description adds value by listing the exact Android CLI subcommands to use, giving the agent a better sense of what goes in the 'command' parameter beyond the schema's single example.

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 Android CLI command and returns stdout', which is a specific verb and resource. It further lists concrete subcommands (e.g., 'android create', 'android run', 'studio analyze-file'), distinguishing it from sibling tools like run_adb or run_bash.

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 'Use for:' line enumerates exact use cases, giving clear context for when to choose this tool. It also mentions the prerequisite of having the Android CLI installed. However, it does not explicitly state when not to use it or name alternatives, though the sibling list implies differentiation.

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