app_stop

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

The description says 'Force-stop' which implies killing the app process. Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, which cover the main behavioral profile. The description adds the force-stop nature but doesn't disclose whether data is lost, whether the app restarts, or effects on background processes. With annotations present, the description carries moderate but acceptable burden.

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 efficient sentence that states exactly what the tool does. No wasted words, front-loaded with the action. Appropriate for a simple tool.

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 (2 params, 1 required, no nesting), has an output schema, and full annotation coverage. The one-liner is arguably sufficient for this complexity level. However, it could mention that serial is optional (defaulting to the primary device) and clarify force-stop semantics versus normal stop. The description is minimally adequate.

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% — both parameters (serial, packageName) are documented in the schema itself. The description adds no additional parameter meaning beyond 'force-stop' framing. Baseline 3 is appropriate when the schema handles parameter documentation.

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 the verb and resource ('Force-stop an app on the device'), which is clear. However, it doesn't differentiate from siblings like app_start or app_uninstall beyond the obvious inverse relationship. It's a clear single-line description but lacks scoping detail.

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?

No guidance on when to use this tool vs alternatives. Nothing mentions that force-stop terminates processes without uninstalling (vs app_uninstall), or that it's for halting a misbehaving app. The openWorldHint=true suggests it may work on unknown devices, but no context for appropriate use cases is given.

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