clear_app_data

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

With no annotations provided, the description carries the full burden, and it does disclose the key behavioral trait: this is a destructive operation that wipes app data, explicitly naming cache, databases, and shared preferences. It does not cover irreversibility or side effects on a running app, but the core destructive scope is clear.

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 one concise, front-loaded sentence with a parenthetical clarifying exactly what data is cleared. Every word earns its place, and there is no redundant 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?

The description is sufficient for a simple two-parameter destructive action, and the schema covers inputs. However, given the large set of sibling tools, it does not provide any guidance on choosing this over uninstall_app or force_stop, nor does it indicate what return or confirmation the caller should expect.

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 100%, so both package and device_id are already documented in the schema. The description adds no extra parameter semantics, but none are needed beyond what the schema provides.

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 a specific action ('Clear all data') and a specific resource ('for an app'), with explicit examples of what is affected: cache, databases, and shared preferences. However, it does not explicitly differentiate itself from sibling tools like uninstall_app or force_stop, which also operate on app state.

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 guidance is given for when to use this tool versus alternatives such as force_stop or uninstall_app. The description does not mention prerequisites, destructive consequences, or when a less invasive operation would be more appropriate.

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