Uninstall a package

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true, so the 'Destructive: the app is deleted' line largely restates structured data. The description does add a concrete consequence (app is deleted from the device) and clarifies keep_data behavior, which is modest value beyond the annotations.

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?

Two tight sentences with the verb and mechanism front-loaded, followed by the destructive consequence and the mitigating option. No filler or redundancy.

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 single-purpose tool with full schema coverage and annotations covering the safety profile, the description is essentially complete. No output schema exists, but the uninstall result is trivial; the only mild gap is lack of explicit routing versus sibling app-state tools.

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%, so the schema already documents device, package, keep_data, and timeout_ms in detail. The description's note about keep_data ('keep its data directory') merely echoes the schema's own description, adding nothing new; baseline 3 applies.

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?

States a specific verb+resource ('Remove an application') and the underlying mechanism (`adb uninstall`), scoping to 'one device'. It is clearly distinct from neighboring tools, though it never explicitly names a sibling it differs from (e.g. 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?

Usage is only implied by the action verb; there is no explicit when-to-use versus alternatives, and notably no guidance distinguishing this from the nearby clear_app_data or force_stop_app tools. The keep_data mention is a parameter hint rather than routing guidance.

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