Stop App

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

No annotations, so the description carries the full burden. 'Force-stop' implies destructive behavior (unsaved state lost, process killed) yet the description never states this, nor whether permissions are needed or what happens on a non-running or nonexistent package.

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?

One front-loaded sentence with zero waste; no filler or restated title.

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 mutation with no annotations and undocumented parameters, the definition is thin. The output schema covers return values, but the missing 'device' semantics and absent force-stop side effects leave gaps an agent needs filled before calling.

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 0% across two parameters. The description clarifies that 'package' is the package name, which adds real meaning over the bare string schema, but the optional 'device' parameter is completely unexplained — an agent cannot tell how to target a specific device.

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?

A specific verb (force-stop) applied to a specific resource (a running app), plus the keying parameter. It is clearly separable from launch_app, uninstall_app, and list_apps in the sibling set.

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 phrase 'a running app' implies the context, but there is no explicit when-to-use guidance, no statement about what happens if the app is not running, and no routing to alternatives such as uninstall_app or launch_app.

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