clear_app_data

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It warns that logins, saves, and cache are lost, that the app is reset to its post-installation state, that ADMIN mode is required, and that confirmation will be requested. This is strong transparency for a destructive 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 compact and front-loaded: the first sentence states the core purpose, and the second concisely adds consequences and requirements. Every sentence earns its place with no padding or repetition.

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 destructive behavior, authentication need, and confirmation are well covered, and an output schema exists for return values. However, the tool has two parameters with no schema descriptions, and the description fails to explain them; usage guidance relative to sibling tools is also absent. Overall it is serviceable but not 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 0%, so the description must compensate, but it only weakly implies that the 'package' parameter identifies the target app. It does not explain the 'serial' parameter, the expected package name format, or how the optional serial affects behavior.

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 operation: deleting all local data of an app, analogous to 'Clear data' in Settings, and explains that the app returns to its fresh-installed state. This is a specific verb and resource, and the 'new state' phrasing helps distinguish it from uninstalling or stopping an app, though no sibling is explicitly named.

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 choose this tool over alternatives like uninstall_app, stop_app, or backup_apps_data. It mentions ADMIN mode and confirmation, but these are prerequisites, not usage-scenario guidance, and no exclusions or alternatives are given.

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