adb_list_apps

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

With no annotations, the description carries the full burden. It conveys that this is a read/list operation and the default filter, but says nothing about needing an active adb connection, what happens if no device is available, or the shape of what is returned (package names vs. richer objects).

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 short sentence with the core behavior and the default scope front-loaded; no filler. It is terse to the point of mild under-specification rather than verbose, which is preferable but leaves little room for the missing prerequisites.

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 two-optional-parameter read tool with no output schema and no annotations, the description covers the essential what and default scope but omits device-connection prerequisites and return format. Adequate to select the tool, thin for invoking it confidently on a multi-device setup.

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 baseline is 3, but the parenthetical adds real meaning the schema lacks: it documents the *default* behavior of the `all` flag (third-party only unless set). The `device` parameter is left entirely to the schema, which is acceptable given full coverage.

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 a specific verb+resource: it lists installed packages, plus the scoping default (third-party only). No sibling tool does anything similar (the other adb_* tools control devices), so the purpose is unambiguous once read, though it doesn't explicitly contrast with adb_list_devices or adb_open_app.

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 explicit when-to-use or when-not-to-use guidance and no mention of the required prerequisite (a connected/authorized device). The only hint is the parenthetical '(third-party by default)', which implies the `all` flag expands scope but doesn't frame it as usage guidance.

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