app_uninstall

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

Annotations already declare destructiveHint=true, so the destructive nature is captured structurally. The description adds no behavioral context beyond what annotations provide — no mention of whether uninstall persists across sessions, requires root/adb permissions, or fails for system apps. With destructiveHint present, the description adds minimal value, though not contradicting anything.

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?

A single, direct sentence that fully conveys the purpose. Zero wasted words. Appropriate for a tool with well-documented schema and annotations.

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 destructive mutation tool with no description beyond one sentence, the description relies heavily on annotations (destructiveHint=true) and 100% schema coverage. There is an output schema present, so return values don't need explanation. However, given it's a destructive action, slightly more context about failure modes (e.g., system apps) would improve completeness.

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 coverage is 100% — both serial and packageName have descriptions in the schema, including a concrete example ('com.example.app'). Description adds no parameter info beyond the schema, so 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 states "Uninstall an app from the device" with a specific verb (uninstall) and resource (app). It's clear and distinguishes from siblings like app_start/app_stop and app_install. However, it doesn't explicitly contrast with app_install which is its direct inverse — though the meaning is obvious enough.

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 doesn't explicitly state when to use this vs alternatives or provide exclusions. Context implies this is for removing an app, and the sibling set makes the purpose reasonably inferable, but no explicit guidance on prerequisites (e.g., app must be installed, permissions needed) is given.

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