Press a hardware button on an iOS Simulator or real iPhone to navigate the device, such as pressing Home to return to the home screen.
Press a hardware button. "home" goes to the home screen.
| Name | Required | Description | Default |
|---|---|---|---|
| button | Yes | ||
| device | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the effect of the home button, but it does not explain device requirements, whether the device must be booted, or any side effects or response behavior.
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 short sentences with the core action front-loaded. Every sentence contributes directly to understanding what the tool does.
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?
For a simple two-parameter tool with no annotations and no output schema, the description is still incomplete: it leaves the 'device' parameter undocumented and omits prerequisites such as whether the target device must already be booted.
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 0%, so the description must compensate. It explains that button='home' goes to the home screen, but it never mentions the optional 'device' parameter or how target selection works.
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 states a specific verb and resource: 'Press a hardware button.' It also identifies the one supported button, 'home', and its effect. It is clear against screen taps, but it does not explicitly name sibling alternatives such as ios_tap.
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?
There is no explicit guidance on when to use this tool versus ios_tap or other iOS interaction tools. The only usage context is the implicit fact that this presses a hardware button, with no exclusions or alternative-routing advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.