android_list_apps

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

No annotations are provided, so the description carries the full burden. It discloses the return content ('package names') but says nothing about ordering, whether it requires a connected device, or that the default behavior filters out system apps — a behavioral trait an agent must know.

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, front-loaded sentence with zero filler; appropriate size for a one-parameter read tool. No structural problems, though there is no routing or constraint information to front-load beyond the core purpose.

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?

Adequate for a simple listing tool with no annotations or output schema, but it omits the most decision-relevant fact — that third-party-only filtering is on by default — and gives no hint about the presence of a device connection requirement. Minimum viable rather than complete.

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 coverage is 100%, so the only parameter (third_party_only, default true) is fully documented in the schema; baseline 3 applies. The description adds nothing about this filter and its wording ('installed applications') could actually imply all apps, mildly clashing with the default filtering behavior.

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?

States a specific verb+resource ('List installed application package names') and is clearly distinguishable from siblings like android_launch_app or android_stop_app, which manipulate rather than enumerate apps. It does not explicitly name a sibling to contrast against, but none of the siblings overlaps its purpose.

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 versus alternatives such as android_shell (which could also enumerate packages) or android_get_ui_tree. No prerequisites or context about when a listing is the right call.

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