as_adb_stop_app

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds 'Does not delete data', which aligns with destructiveHint=false. However, it does not disclose potential side effects like losing unsaved app data or killing background services, which would add value beyond annotations.

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 short and direct: two sentences plus structured args/returns. It is front-loaded with the key purpose. No redundant information, though it could be slightly more structured with a usage note. Overall 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?

Given the tool's simplicity (force-stop, one parameter, output schema present), the description covers the essential behavior and return format. It omits aspects like device connection requirements or error handling, but the annotations and schema compensate. For a low-complexity tool, it is reasonably complete.

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?

Although the tool description has 0% param coverage, the input schema provides detailed descriptions for serial, package, and confirm. The description adds 'confirm not required', which clarifies usage beyond the schema. Baseline is 3 due to high schema coverage, and the added hint justifies a 4.

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 explicitly states 'Force-stop an app (am force-stop). Does not delete data.' This clearly identifies the action (force-stop) and the target (app). It distinguishes from siblings like as_adb_start_app and as_adb_uninstall by specifying no data deletion.

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 mentions 'confirm not required' but does not provide explicit when-to-use guidance or alternatives. It implies usage for force-stopping, but lacks context such as prerequisites or comparison to related tools like as_adb_uninstall. Sibling differentiation is minimal.

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