Navigate an Android device to the home screen by simulating the home button press via ADB.
Press the home button
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "adb_press_home"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| deviceId | No | Target device ID (optional) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral transparency. 'Press the home button' describes the action but does not disclose potential side effects (e.g., screen state, key event details, or device selection behavior). For a simple input action, this is adequate but minimal.
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, concise sentence that fully communicates the tool's purpose without any waste. It is front-loaded and easy to parse.
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 (one optional parameter, no output schema), the description is nearly complete. However, it does not mention behavior when deviceId is omitted or how the action behaves across multiple connected devices, though this is partially inferred from the sibling tools.
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 single parameter deviceId is fully described in the schema (coverage 100%), so the description adds no additional meaning. The baseline of 3 applies because the schema handles parameter semantics completely.
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 'Press the home button' uses a specific verb and resource, clearly distinguishing it from siblings like adb_press_back and adb_tap. It directly matches the tool name while adding the object 'button', making the purpose unambiguous.
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 pressing the home button but does not explicitly contrast with alternatives like adb_press_key or adb_press_back. There is no when/when-not guidance, so the usage is inferred from the name rather than explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.