Clear an app's stored data on Android or iOS simulator to reset it to a first-run state by specifying platform and app ID.
Reset app data (clear storage) for a mobile app on Android or iOS simulator
| Name | Required | Description | Default |
|---|---|---|---|
| appId | Yes | Android package name or iOS bundle id | |
| deviceId | No | Device UDID (iOS) or Serial (Android). Defaults to booted/connected. | |
| platform | Yes |
Changes observed during successful MCP inspections.
v0.34.0Input schema / allOfAdded value: +[
+ {
+ "not": {
+ "required": [
+ "expectedState"
+ ]
+ }
+ }
+]v0.31.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since there are no annotations, the description must carry the behavioral load. Explicitly stating 'on Android or iOS simulator' is critical behavioral context, as resetting data on a physical device would be a much more sensitive operation than resetting a simulation environment.
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 definition is highly efficient. It is a single, front-loaded sentence that conveys the core function and necessary scope without any filler.
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?
While it specifies the operation and the environment (simulators), it lacks full context for a destructive action. It doesn't specify if the tool returns a success/failure status or if the action is immediate.
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?
With schema coverage at 67%, the description is baseline. It does not add specific semantic meaning to the parameters (appId, deviceId, platform) beyond what the schema already dictates, neither compensating for the gaps nor providing extra clarity.
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 purpose as 'Reset app data' and clarifies the mechanism ('clear storage'). It specifies the target (mobile app) but doesn't explicitly differentiate it from functionally similar tools like `terminate_app` found in the sibling list, preventing a perfect score.
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 provides almost no guidance on usage context. It doesn't explain when this is the correct choice (e.g., testing data corruption) versus when a different tool might be appropriate (e.g., reinstall_app).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.