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 behavioral burden, and it discloses nothing. It does not say whether uninstalling deletes associated data, whether it is reversible, whether it requires the app to be stopped, or what permissions are needed. For a destructive operation this is a serious gap.

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 two words with no wasted text, but the brevity reflects under-specification rather than disciplined concision. Nothing is front-loaded or expanded because no content exists.

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, parameterized tool with no annotations, no output schema, and an undocumented required parameter, the description is completely inadequate. An agent would have to guess at both the target identifier and the consequences of the call.

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?

The single required parameter 'id' has 0% schema description coverage, and the description does not explain what the id refers to (app id vs name vs slug) or where to obtain it. The description must compensate for the coverage gap and does not.

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 phrase 'Uninstall app' names a verb and a resource, so the agent knows the general action. However, it is essentially a restatement of the tool name 'uninstall_app' and offers no differentiation from siblings such as install_app, update_app, or list_installed_apps. It is the minimum viable purpose statement.

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?

There is no guidance on when to use this tool versus update_app, install_app, or other removal tools, nor any preconditions (e.g., app must be stopped, data impact). The description provides no usage context whatsoever.

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