uninstall_app

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

No annotations are present, so the description carries the safety burden. 'Uninstall' clearly signals destructive removal, but the description does not explicitly mention that app data is deleted or that the operation is irreversible, which would strengthen transparency.

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?

One front-loaded sentence with no filler. Every word contributes to identifying the action, the target, and the environment.

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 two-parameter tool with a fully documented schema, the description plus schema is sufficient for correct invocation. It could add a note about return values or data-loss side effects, but those are refinements rather than missing essentials.

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?

The input schema already documents both package and device_id with 100% coverage. The description adds no parameter-level meaning beyond what the schema provides, so it earns the baseline score for fully covered schemas.

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 the specific action 'Uninstall' and the resource 'app', scoped to 'a connected Android device'. This is clearly distinct from sibling tools like install_apk, clear_app_data, and force_stop.

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 gives clear context: use it when you need to remove an app from an attached Android device. It does not name alternatives or exclusions, such as using clear_app_data when the app should remain installed, so it stops short of explicit when-not guidance.

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