uninstall_appPermanently remove a Homey app and all its associated devices. This action cannot be undone.
Permanently uninstall a Homey app and remove all its devices. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | App ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond the destructiveHint annotation by disclosing that it removes the app's devices and that the operation is irreversible. This gives the agent crucial context about side effects.
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 one concise sentence that conveys the purpose, scope, and irreversibility without waste. It is front-loaded and easy to parse.
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 simple tool with one parameter and no output schema, the description is complete. It specifies the action, the target, the side effect (device removal), and the irreversibility. It does not mention permissions or other edge cases, but these are not critical given the tool's simplicity.
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 schema has one parameter 'id' with a description 'App ID', which fully covers the parameter. The description adds no additional parameter semantics, so the baseline of 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?
The description clearly states the tool's verb ('uninstall'), the resource ('Homey app'), and the scope ('and remove all its devices'). It distinguishes itself from sibling tools like restart_app or enable_app by emphasizing permanent 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 context is clear: this is for permanently removing an app. The phrase 'cannot be undone' implicitly warns against using it for temporary actions, but it does not explicitly name alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.