stop_app

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

With no annotations, the description carries the full burden of behavioral disclosure. It says the tool stops the app process but does not explain what happens if no app is running, whether the stop is forceful, whether app state is lost, or how the simulator behaves afterward.

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 definition is a single, front-loaded sentence with no redundant wording. Every part of the sentence contributes to identifying the action and target.

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 zero-parameter lifecycle tool, the description is minimally adequate: it identifies the target process and the simulator context. However, given the absence of annotations and an output schema, it should say more about side effects and preconditions to be fully 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?

The tool takes zero parameters, so the baseline is 4. The description correctly does not invent parameter details and focuses on the action itself.

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 uses a specific verb ("Stop") and resource ("currently running Garmin Monkey C app process in the simulator"), which clearly identifies the operation. It implicitly distinguishes itself from terminate_simulator by scoping the action to the app process rather than the simulator, though it does not explicitly name the sibling.

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 implies when the tool is useful: when a Monkey C app process is currently running in the simulator and needs to be stopped. It does not state exclusions, prerequisites, or explicitly contrast this with alternatives such as terminate_simulator or run_app.

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