Uninstall an app

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

The annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds critical context: 'deletes the app's data and cannot be undone', the effect of keep_data ('adb uninstall -k'), and error behavior ('Reports when the package was not installed to begin with'). No contradictions with 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?

Structured with clear sections (Description, Args, Returns, Examples, Error Handling). Front-loaded with the core purpose and destructive warning. Every sentence contributes useful information without 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?

Given the tool's complexity (5 parameters, no output schema), the description covers the return format, example use cases, error handling, and parameter resolution logic. It is self-contained and fully prepares the agent to invoke the tool correctly.

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?

While schema coverage is 100%, the description adds relational semantics: 'project_path... package is resolved from it when package_name is omitted' and clarifies keep_data as 'keep app data and cache directories (adb uninstall -k)'. This goes beyond the schema's per-field definitions.

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 opens with 'Remove an app from the device', which is a specific verb+resource statement. It further clarifies destructive consequences and distinguishes from sibling tools like android_clear_data by explicitly stating when uninstall is appropriate (e.g., INSTALL_FAILED_UPDATE_INCOMPATIBLE) versus when a less destructive alternative should be used.

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?

Provides explicit use cases: 'Use when: an install fails with INSTALL_FAILED_UPDATE_INCOMPATIBLE...' and 'Use when: testing a first-run experience'. It also gives a clear exclusion: 'Don't use when: you only want to clear state; force-stopping or clearing data is less destructive', naming the alternative.

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