deploy_to_android

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

With no annotations, the description must disclose behavioral traits. It explicitly warns that the operation 'blocks the editor while running,' which is a valuable side-effect disclosure. However, it doesn't mention prerequisites like a connected device, failure modes, or permissions. The description adds some behavioral context beyond the name, but not comprehensively.

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?

One concise sentence, front-loaded with the main action, and no redundancy. Efficient and to the point.

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 is a multi-step deployment operation with six optional parameters and no output schema. The single-sentence description provides an overview but lacks essential details about parameter semantics, prerequisites, device selection, and expected output. It covers blocking behavior but is insufficient for correct usage.

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 six parameters with zero description coverage, and the description does not explain any of them. It fails to clarify the meaning of debug, launch, preset_name, skip_export, preset_index, or device_serial, leaving users without guidance on parameter usage.

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 specifies a three-step process: export APK, adb-install, and launch on a device. It distinguishes itself from sibling tools like export_project and list_android_devices by including installation and launch, and it identifies the resource (Android device).

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?

No explicit when-to-use or alternative guidance is provided. The usage is implied through the described sequence, but there's no mention of when this tool should be preferred over export_project or list_android_devices, nor any exclusions.

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