reset_app_data

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only says 'clear storage' but does not elaborate on what data is removed (e.g., cache, user defaults), whether the app is terminated, or if the action is reversible. The description is insufficient given the potentially destructive nature of the operation.

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 very concise (one sentence), but it sacrifices important details for brevity. It would benefit from additional context about the action's impact, which could be added without becoming overly verbose.

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 has moderate complexity with three parameters and no output schema. The description omits important context such as what happens after the reset (e.g., app restarts, data is lost permanently) and prerequisites (e.g., app must be installed). This gap leads to an incomplete understanding for the agent.

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 67% (two of three parameters have descriptions). The tool description adds no further parameter semantics beyond the schema, but the existing schema descriptions are adequate. Baseline score of 3 is appropriate.

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 action 'reset app data (clear storage)' and the target 'mobile app on Android or iOS simulator'. It uses a specific verb and resource, distinguishing it from sibling tools like start_app or get_logs.

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 no guidance on when to use this tool versus alternatives such as reinstalling the app or using other reset methods. It does not mention that this is a destructive action or suggest use cases like simulating a fresh install.

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