List Android packages

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say how the target device is chosen when serial/deviceId/deviceName are all omitted, nor whether the filter is a substring, regex, or package prefix match.

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 no filler, and the core action plus both filter axes are stated up front. It is efficient, though the brevity is partly what creates the documentation gaps.

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 five-parameter tool with 0% schema coverage and no output schema, the description is too thin. Device selection semantics, filter matching behavior, and any notion of result ordering or size are all missing, so an agent cannot call it confidently beyond the happy path.

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 five parameters, so the description must carry the load. It only loosely gestures at two of them (thirdPartyOnly via 'third-party', filter via 'text filtering') and says nothing about the three device-targeting parameters or their precedence, leaving the agent to guess.

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 (List) and resource (installed Android packages) plus the filtering dimensions, so it is immediately distinguishable from mutation siblings like adb_install/adb_uninstall. It does not explicitly differentiate itself from nearby read siblings such as adb_app or adb_devices, which keeps it below a 5.

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 never says when to pick this over adb_app, adb_devices, or adb_shell, nor does it state prerequisites such as needing a connected device or an active adb server. Usage is only implied by the word 'List'.

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