App Uninstall

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

No annotations are provided, so the description carries the full behavioral burden. It does flag the tool as a write operation ('写操作'), which is a minimal but useful signal, yet for an uninstall tool it omits the critical traits: irreversibility, whether app data/config is destroyed, permission requirements, or any confirmation/rate behavior.

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 short sentence with zero filler, and the write-operation warning is front-loaded. It is efficiently sized, though the extreme brevity borders on under-specification rather than genuine conciseness.

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?

This is a destructive mutation tool with no annotations, and the description says only that it uninstalls and is a write operation. An output schema exists, so return values need not be explained, but the absence of any warning about data loss, permissions, or irreversibility leaves the definition incomplete for its complexity.

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%, and the schema itself documents app_name carefully (sourced from app_list's appName, not the display name) plus host/port/scheme/profile. The description adds nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('卸载应用' / uninstall app), so an agent knows exactly what operation is performed and can distinguish it from siblings like app_install, app_start, or app_stop. It does not, however, explicitly differentiate itself from those siblings or clarify scope (e.g., data removal).

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 gives no when-to-use guidance, no prerequisites, and names no alternatives. An agent is left to infer that this is the inverse of app_install purely from the name, with nothing about confirmation, dependencies, or when uninstall is appropriate versus stopping the app.

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