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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the agent knows this mutates the device and is repeatable. The description adds nothing beyond that—it never states what is destroyed (app data, cache), whether the app must be stopped first, or that the operation may be irreversible.

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?

A single front-loaded sentence with a clear verb-resource-target structure and zero filler. Nothing is padded or redundant.

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 tool with rich annotations and no output schema, the one-line description is minimally adequate. However, it omits practical context such as data-loss implications and the relationship to device_terminate_app, which an agent choosing between the two would want.

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 both udid and packageName are fully documented inline; baseline 3 applies. The phrase 'by package name' loosely echoes the packageName parameter but adds no format or syntax detail beyond the schema's own example (com.example.app).

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 (uninstall) and resource (app) and scopes it to 'an Android device by package name', which implicitly distinguishes it from the sibling ios_uninstall_app. The identification method (package name) also sharpens the purpose, though no sibling is named explicitly.

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?

No when-to-use guidance is given. It does not explain how it differs from the closely related sibling device_terminate_app (terminate a running app vs. fully remove it), nor does it mention prerequisites such as the app being installed or a device being connected.

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