Force-stop Android app

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

Annotations declare the safety profile (idempotentHint=true, destructiveHint=false, readOnlyHint=false), and the description adds real value beyond them by naming what actually gets terminated: the package's processes and pending implicit launches. It still omits permission requirements and whether the app is removed from recents, but it meaningfully extends the annotation-covered profile.

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?

A single front-loaded sentence with the action first and the scope qualifier second. No filler, no redundancy.

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?

An output schema exists so return values need not be described, and annotations cover safety, but with an undocumented userId and packageName the definition leaves gaps an agent must resolve. Adequate but incomplete for a 3-param mutation tool.

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 only 33% (serial documented; userId and packageName bare except for a pattern/default), so the description carries the burden to compensate but adds no parameter meaning at all. Neither how userId='current' behaves nor the packageName format is explained in prose.

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?

Specific verb 'force-stop' plus resource 'package', with added scope ('processes and pending implicit launches') that clarifies what stopping entails. It does not explicitly differentiate from near siblings like mobile_app_uninstall or mobile_app_relaunch_on_displays, but the action is unambiguous.

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?

No statement of when to use this versus alternatives (e.g., uninstall, relaunch, or launch/reset flows), no prerequisites, and no note that the app must be installed/running. The agent must infer all usage context from the name alone.

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