stop_app

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

With no annotations, the description carries the behavioral burden itself. It transparently states that it both closes the browser page and stops the app process, which is meaningful for an agent deciding whether this operation is appropriate. It does not mention effects of stopping an app not previously launched or whether the operation is reversible, but the core behavior is disclosed.

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, compact sentence with no filler. The close action is front-loaded, and the 'for launched apps' qualifier clarifies scope without adding unnecessary detail.

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?

The tool is simple, with one parameter and no output schema, so the description covers the basic purpose. However, it is missing guidance on where app_id comes from, when the browser-page-close behavior occurs, and what happens for apps that were not launched by this system, leaving meaningful gaps.

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%, and the description never mentions app_id or how it should be obtained. The agent is left to infer that app_id identifies the launched app, with no guidance on its format or relationship to sibling tools like launch_app.

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 pair — closing the browser page and stopping the launched app process — which clearly identifies the tool's purpose. It also differentiates itself from the sibling launch_app by describing the inverse lifecycle operation.

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 'for launched apps' implies the tool is used when an app was started with launch_app, but it doesn't explicitly state when to use this tool versus alternatives or when not to use it. No exclusion criteria or fallback options are provided.

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