How should Android automation apps explain AccessibilityService?

Android touch automation needs AccessibilityService to dispatch user-configured gestures, but the system warning is necessarily broad.

For Phone Operator, I currently show a disclosure before opening Android settings, explain what the service does and does not do, require the user to start every run, keep a visible stop controller and foreground notification, and provide a direct path to disable the service. Scripts stay on the device unless the user explicitly shares one.

I am trying to balance meaningful consent with an onboarding flow that does not overwhelm first-time users. For Android users and developers, which signals matter most before you would grant this access: no screen-content collection, local-only scripts, a visible stop control, a short test mode, or something else?

I will use the feedback to improve the permission guide and onboarding.