Uninstall App [Pro]

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

The description clearly discloses that the tool removes the app and all its data, which is critical behavioral information. It also warns about system apps requiring root access. Without annotations, the description carries the burden; it meets it well.

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 concise (two sentences) and front-loaded with the core purpose. It wastes no words, though the '[Pro]' prefix is minor noise. Still, every sentence adds value.

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 simplicity (2 parameters, no output schema, no nested objects), the description is adequate. It covers purpose, effect, and a key limitation (system apps). No major gaps are present.

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%, with 'device_id' and 'package_name' clearly documented. The description adds context about 'package name' but does not provide additional semantics beyond the schema; baseline 3 is appropriate.

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 specific verbs ('uninstall', 'removes') and clearly identifies the resource (application by package name). It distinguishes this tool from siblings like 'stop_app' or 'install_app' by focusing on removal and data deletion.

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 implicitly states when to use (to uninstall an app) and explicitly notes a limitation: system apps cannot be uninstalled without root access. However, it does not explicitly mention when not to use or compare with alternative tools like 'stop_app'.

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