clear_app_data

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

With no annotations, the description carries the full burden. It communicates the destructive effect ('Clear all data and cache') and the consequence ('Resets the app to a fresh-install state'). However, it does not explicitly warn about irreversibility, permissions, or platform-specific behavior (especially on iOS, where 'Clear Data' is not a standard concept), leaving meaningful gaps.

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?

Three sentences, with the action in the first sentence, followed by the reset consequence and then use cases. No fluff or redundancy; appropriately front-loaded and efficient.

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 is simple and has no output schema, so return values need no explanation. Still, the description omits important context: it mentions an Android-specific settings path even though platform includes iOS, and it does not mention prerequisites like the app being installed. This is adequate but not fully complete.

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 only 33% (only packageId is documented). The description adds no parameter-specific guidance: nothing about how deviceId is used or how platform affects behavior. It fails to compensate for the low schema coverage.

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 action ('Clear all data and cache') and resource (an app), clarifies it as equivalent to Settings → App → Clear Data, and adds the fresh-install reset outcome. This clearly distinguishes it from sibling tools like manage_app_lifecycle or get_app_info.

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?

It provides a direct use case: 'Useful for testing onboarding or reproducing first-launch bugs,' which tells an agent when to use it. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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