Force-stop Android app

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

The description adds context beyond annotations: it mentions including 'processes and pending implicit launches', which explains the scope of the stop action. Annotations already indicate idempotentHint=true and destructiveHint=false, and the description does not contradict these. However, it does not disclose potential side effects like loss of unsaved data or app state.

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 very short (one sentence), which is concise, but it lacks important details such as parameter hints or usage context. It is minimal but not optimally informative.

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 has an output schema (not shown in the provided data) but the description does not mention return values or behavior. For a force-stop operation, details about confirmation, error handling, or impact on other processes are missing, leaving the description incomplete.

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 only 33% (only 'serial' has a description). The tool description does not mention any parameters or provide additional meaning beyond the schema. For a tool with low coverage, the description should compensate, but it fails to do so.

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 title 'Force-stop Android app' and description 'Force-stop a package, including its processes and pending implicit launches' clearly specify the verb (force-stop) and resource (package). This effectively distinguishes it from sibling tools like mobile_app_launch or mobile_app_install.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or scenarios. The agent is left to infer usage from the name alone.

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