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 transparency burden. It clearly discloses the destructive nature ('Clear all data') and the resulting state ('fresh-install state'), indicating irreversibility. It could mention additional effects like clearing permissions or requiring the app to be stopped, but the core behavior is transparent.

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, front-loaded sentence that conveys the essence without waste. The parenthetical 'pm clear' adds useful technical context, and the dash clause clarifies the outcome. Every word earns its place.

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?

For a simple tool with two optional parameters and no output schema, the description is largely complete. It explains what happens and the end state. It could add more about when to use it (e.g., for resetting an app's state before testing), but the core semantics are sufficiently clear for an agent to invoke the tool correctly.

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% for both parameters (appId and serial), so the baseline is 3. The description does not add any parameter-specific meaning beyond the schema, but that is acceptable given the high 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?

Clearly states the action: 'Clear all data of an app' with the specific resource 'app' and the effect 'resets it to a fresh-install state.' The mention of 'pm clear' further anchors the operation, distinguishing it from sibling tools like uninstall_app or stop_app.

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 implies usage by stating it resets to fresh-install, but it does not explicitly say when to use this tool vs alternatives such as uninstall_app or clear only specific data. No exclusions or alternative references are provided, making it an implied but not fully guided usage.

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