uninstall_app

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

With no annotations, the description carries the behavioral burden. It discloses two important behavioral traits: ADMIN mode is required and confirmation will be requested. For a destructive uninstall operation, this is meaningful transparency, though it does not mention irreversibility or data deletion effects.

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: the action and target come first, followed by the key requirements. No filler or redundant information is present.

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 description covers the core operation and critical prerequisites, and the output schema exists so return values need not be explained. However, it omits guidance on the serial parameter, fails to mention alternative paths, and does not warn about permanent data loss, leaving an otherwise minimal description only partially 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. It adds the insight that the app is identified by package name, which relates to the required 'package' parameter, but the optional 'serial' parameter is not explained at all. This is only partial compensation for the schema gap.

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 explicitly states a specific action (removal/uninstall) applied to a specific resource (application), and identifies the key selection criterion (package name). This clearly separates it from siblings like install_apk, stop_app, and clear_app_data.

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?

Using the tool is implied: it removes an app by package name. However, there is no explicit guidance on when to choose this over alternatives such as stop_app or clear_app_data, and no stated exclusion conditions. The ADMIN mode requirement is a precondition, not usage direction.

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