uninstall_app

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that uninstalling removes app data or that it is a destructive, irreversible operation, nor any prerequisites beyond 'connected device.'

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, clear sentence that is appropriately sized and directly states the tool's function with no filler words.

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 uninstall operation with 3 parameters fully described in the schema, the description is minimally adequate but does not explain when to prefer this over related tools like clear_app_data, nor does it highlight the data-loss implication. It lacks context for an agent making a nuanced choice.

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?

All three parameters (serial, keepData, packageName) are fully described in the schema, so the description adds no additional parameter semantics. The description does not elaborate on the keepData flag or serial selection, but schema coverage is high at 100%.

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 uses the specific verb 'Uninstall' and identifies the resource 'application package from the connected device,' which clearly states what the tool does and distinguishes it from sibling tools like install_app or 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?

The description provides no guidance on when to use this tool compared to alternatives such as clear_app_data or force_stop_app. It only states the basic action without exclusions or context for selection.

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