app_action

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

With no annotations, the description carries the full behavioral burden. It does one genuinely useful thing: disclosing that clear/uninstall remove user data, and that downgrade/test/permission behaviors are explicit opt-in switches. However, it says nothing about root/privilege requirements, what launch/stop do to running state, whether install replaces existing data, or side effects of enable/disable.

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?

It is short and front-loads the action inventory, with no filler sentences. The dense slash-separated style sacrifices readability for brevity and forces the agent to parse a token stream rather than read structured statements.

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 9-parameter, no-annotation, multi-mode tool, the definition is thin: an output schema exists so return values need not be described, but action semantics, parameter roles, and privilege requirements are all missing. The action enumeration is the only substantive content.

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% across 9 parameters, so the description must compensate. It partially does: 'apk_paths (base+splits)' maps to apk_paths, and 'explicit downgrade/test/permission switches' maps to allow_downgrade, allow_test, grant_permissions. But action (the primary discriminator), package, user_id, activity, and include_system are given no meaning at all.

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 names a specific resource (apps) and enumerates the concrete verbs it supports: list/info/paths/launch/stop/restart/clear/enable/disable/uninstall plus install/install_multiple. An agent can tell this is the app-lifecycle tool. It does not distinguish itself from siblings like manage_app, app_permissions, or deploy_and_verify_apk, which appear to overlap.

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?

There is no when-to-use guidance, no preconditions, and no routing to alternatives despite several overlapping siblings (manage_app, app_permissions, export_apks, deploy_and_verify_apk). The agent must infer action selection entirely from the slash-separated verb list.

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