Terminate App

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which tells the agent it mutates state without destroying data. The description adds no further behavioral context, such as force-stop semantics, loss of unsaved app state, or whether the app can be relaunched afterward. It essentially restates the action already implied by the annotations.

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?

Two sentences with no filler. The action is front-loaded, and the identification methods are concise. Every word earns its place.

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?

The tool is simple, but the description does not address whether at least one of appName or packageName is required, even though the schema lists only device as required. This is a notable gap for correct invocation. It also lacks any mention of behavior when the app is not running or when both identifiers conflict. Adequate but with clear gaps.

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%, so baseline is 3. The description adds value by clarifying that appName and packageName are alternative identification methods ('Identify it by package name or by its current device-locale label'), which is not explicit in the schema. This helps agents understand they can use one or the other (or both), improving parameter understanding beyond schema text.

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 a specific action ('Stop and terminate an app') and a clear resource ('on mobile device'), and it distinguishes from siblings by noting the two identification methods (package name or locale label). This unambiguously differentiates it from launch, uninstall, or restore tools.

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 implies when to use the tool: when you need to stop an app. However, it does not explicitly mention alternatives or exclusions, such as 'use uninstall instead of terminate if you want to remove the app' or when to use mobile_restore_previous_app. It provides clear context but no exclusionary guidance.

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