adb_force_stop

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

The description says 'Force-stop an app immediately,' which indicates a destructive action, but it does not elaborate on side effects (e.g., data loss, impact on background services) or any prerequisites. Given no annotations, the description partially covers behavioral traits but lacks detail.

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 very concise with two short sentences, no redundancy. It could be slightly more informative without violating conciseness, but it is efficient.

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 tool with one required parameter and no output schema, the description is minimally adequate but lacks context about return behavior, potential errors, or prerequisites (e.g., app must be installed). It does not leverage the opportunity to add value beyond the schema.

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?

Both parameters (packageName, device) are fully described in the input schema with example and serial meaning. The description adds no further semantic value beyond the schema, and coverage is 100%, so baseline 3 applies.

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?

Description clearly states the tool force-stops an app immediately, and it distinguishes itself from sibling tools like adb_start_app, adb_restart_app, and adb_clear_data by specifying the action and its common use.

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 'The most common debugging action' implies frequent usage but does not provide explicit guidance on when to use vs. alternatives or when not to use it. No exclusion criteria are mentioned.

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