clear_app_data

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

destructiveHint=true already flags destructiveness, and the description adds value by specifying exactly what is destroyed: all app data and permissions. It also conveys the post-condition of resembling a fresh install, which is useful behavioral context beyond the annotation. It does not mention force-stopping or irreversibility, but the annotation and 'clear all data' cover the main risk.

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 sentence that front-loads the action and scope, and the parenthetical analogy adds meaning without extra words. Every part 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 two-parameter destructive tool with no output schema, the core semantics are present and the destructive annotation covers safety. However, the description omits practical invocation guidance such as how the package is specified, that the app remains installed, and what the command returns or emits on success.

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 50% and the package property has no description. The description contributes no parameter-level detail: it does not explain what a package name should look like or that serial is optional. With low schema coverage, the description needed to compensate and did not.

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 ('Clear') and a precise resource ('all data and permissions for an app'), and the 'like a fresh install' analogy clarifies that the app itself is kept, distinguishing it from the nearby uninstall_app. An agent can tell what this tool does without relying on the name alone.

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 fresh-install analogy implies the intended use case of resetting app state while keeping the app installed, but it never explicitly states when to prefer this over uninstall/reinstall or gives exclusions. The guidance is implied rather than spelled out.

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