Terminate App

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

Annotations already mark the operation as non-read-only and non-destructive, but the description adds little beyond the basic 'terminate' behavior. It does not disclose details such as whether the app is force-stopped, whether background processes are killed, or whether unsaved state is discarded.

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 appropriately short for a simple tool. The phrase 'Stop and terminate' is slightly redundant, but the sentence is front-loaded and contains no unnecessary filler.

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 two-parameter action with a complete schema and no output schema, the description is minimally viable. However, it omits any note about side effects, success behavior, or relation to the app lifecycle, so an agent gets only the most basic context.

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 the parameters device and packageName are fully documented there. The tool description adds no additional semantic detail, so it stays at the baseline 3.

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 action ('terminate an app') and resource ('app on mobile device'). It is distinguishable from siblings like mobile_uninstall_app and mobile_launch_app by the verb, though it does not explicitly name or contrast those alternatives.

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 alternatives such as mobile_uninstall_app or mobile_launch_app. The description says only what the tool does, not when it should be selected.

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