uninstall_app

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

No annotations are provided, so the description carries the full burden. 'Uninstall an app' implies a destructive mutation, but it doesn't disclose critical behavioral traits such as whether this requires specific permissions (e.g., root access), if the action is reversible, potential side effects (e.g., data loss), or error conditions (e.g., app not found). The description is too vague for a mutation tool.

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 extremely concise with a single sentence, 'Uninstall an app', which is front-loaded and wastes no words. While it may be under-specified, it earns full marks for brevity and clarity within its limited scope.

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 complexity of an uninstall operation (a destructive mutation), lack of annotations, 0% schema coverage, and presence of an output schema (which might help but isn't described), the description is incomplete. It fails to address key aspects like behavioral risks, parameter usage, or context within sibling tools, making it inadequate for safe and effective use.

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 0%, meaning parameters are undocumented in the schema. The description adds no information about parameters like 'package_name' (what format, where to find it) or 'device_serial' (when to specify it, default behavior). For a tool with 2 parameters and no schema documentation, this is insufficient to compensate.

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 'Uninstall an app' clearly states the action (uninstall) and target (app), which is better than a tautology. However, it lacks specificity about what kind of app (e.g., Android app via package name) and doesn't distinguish it from sibling tools like 'clear_app_data' or 'force_stop_app', which also manage apps but perform different operations.

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 versus alternatives. It doesn't mention prerequisites (e.g., needing an installed app), exclusions (e.g., system apps might not be uninstallable), or related tools like 'install_apk' for installation or 'clear_app_data' for data removal without uninstallation.

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