force_stop_app

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only repeats the tool's name ('Force stop') without explaining side effects like killing background processes, potential data loss, or whether it affects other apps. It adds little beyond what the tool name already implies.

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?

It is a single, clear sentence with no unnecessary words. The action and target are immediately stated, making it efficiently front-loaded.

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 description is minimal, lacking usage context, side effects, or relationship to sibling tools. Given that force-stopping is a potentially destructive operation and no output schema or annotations exist, the description should provide more cautionary context and clarify differences from related tools.

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 input schema provides complete descriptions for both parameters (serial and packageName), so baseline is 3. The description adds no extra parameter-level context, but the schema is sufficient, so the tool description doesn't need to compensate.

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 ('Force stop') and the target resource ('all processes associated with the application package'). It distinguishes itself from sibling tools like uninstall_app (removes the app) and clear_app_data (clears app data), which are related but different operations.

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 provides no guidance on when to use this tool instead of alternatives. It does not mention typical use cases (e.g., unresponsive app) or contrast with similar operations like uninstall or clear data. No exclusions or conditionals are mentioned.

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