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 of disclosure. It clearly states the tool is destructive ('Wipe an app's data and cache'), implies no rollback, and uses the phrase 'from scratch' to convey irreversibility. A 4 is appropriate because it effectively communicates the mutation behavior, though it could mention potential side effects (e.g., login tokens lost).

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, tight sentence that conveys purpose, mechanism, effect, and use case without any wasted words. It is front-loaded with the key action and parenthetical command, making it immediately scannable.

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 no output schema, the description could mention what the tool returns (e.g., success/failure message), but for a destructive command like 'pm clear', the effect is the primary concern. The description completely covers intent and behavior for an agent, earning a 4 for being nearly complete in context.

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 the baseline is 3. The description adds value by explaining the purpose ('reset to first-launch state') and the underlying command ('pm clear'), but it does not elaborate on parameter details beyond what the schema provides, such as the optional nature of 'serial' or format of 'package'.

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 uses a specific verb-resource pair ('Wipe an app's data and cache') and clearly identifies the tool as a 'pm clear' equivalent. It explains the effect ('reset to a first-launch state') and the use case ('reproduce onboarding/permission flows'). This distinguishes it from siblings like 'uninstall_app', 'stop_app', 'clear_logcat', and 'clear_device_lock'.

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 explicitly states the use case ('fastest way to reproduce onboarding/permission flows'), providing clear context for when to use this tool. However, it does not mention when not to use it or explicitly name alternatives among the siblings, such as 'uninstall_app' or 'stop_app' for less destructive resets.

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