stop_app

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

With no annotations provided, the description must fully disclose behavior. 'Force-stop' implies abrupt termination, but it doesn't clarify consequences like unsaved data loss, required permissions, or what happens if the app isn't running. It is adequate but could be more explicit.

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 extremely concise: two sentences, no unnecessary words. The first sentence states the core purpose, the second adds a practical usage hint. Every sentence earns its place.

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, good schema, and no output schema requirement, the description is sufficiently complete. It covers the primary action and a key usage scenario. Minor gap: it doesn't mention that this is Android-specific, but the sibling tools make that clear.

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 100% with clear descriptions for both parameters (serial and package). The description adds no additional semantic value beyond restating 'by package name'. Baseline 3 is appropriate since schema already handles the meaning.

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 resource (app) with a specific verb. It distinguishes from siblings like clear_app_data or uninstall_app by mentioning pairing with launch_app for resetting.

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 explicitly suggests pairing with launch_app 'when reproducing a bug', giving a concrete use case. However, it doesn't mention when not to use this tool (e.g., for apps that should remain running) or alternative tools for graceful shutdown.

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