stop_app

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

With no annotations provided, the description itself must convey behavioral implications. 'Force-stop' does signal a terminating/destructive action, but it does not disclose potential side effects (e.g., loss of unsaved state, effect on background processes, behavior if the package is missing). The core behavior is transparent, but the consequences are not fully addressed.

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 sentence contains the verb, target, and parameter relation with no filler. It is front-loaded and easily parsed by an agent.

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 one-parameter force-stop operation with an output schema available, the description plus schema provide enough to call the tool correctly. It misses minor context such as error handling and side-effect caveats, but these are not essential for basic invocation.

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 0%, so the parameter meaning relies on this description. The phrase 'by package name' directly connects the sole required parameter to the action, and although it lacks a format example, a single self-explanatory parameter makes correct invocation straightforward.

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 states a specific action (force-stop), a resource (app), and the key discriminator (package name). This clearly distinguishes the tool from siblings like start_app and clear_app_data without requiring schema inspection.

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 operation's purpose is clear, but there is no explicit when-to-use guidance or stated alternatives. Usage is implied by the phrase 'force-stop an app', which is sufficient for simple cases but does not explain when to prefer this over clear_app_data or start_app.

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