adb_list_packages

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

With no annotations, the description carries the behavioral disclosure burden. It correctly implies a read-only listing operation and hints at default behavior by describing the option to include system packages. However, it does not mention output format, device connection requirements, or any caveats about how the filter behaves, leaving some gaps.

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?

The description is a single compact sentence that leads with the core action and resource, then covers both configurable options without extraneous detail. It is well-structured and easy to scan.

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?

The tool is simple and the parameters are fully described, but there is no output schema and no mention of what the tool returns or what prerequisites exist, such as a connected Android device. The description is adequate for a basic list operation but could be more self-contained.

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?

The input schema already covers both parameters fully with 100% coverage. The description restates the same concepts, adding no deeper semantic meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Lista') and resource ('paquetes instalados del dispositivo Android'), clearly stating what the tool does. It also mentions the two key capabilities, filtering by name and including system packages, which distinguishes it from unrelated siblings like adb_get_logcat or adb_dump_hierarchy.

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 provides clear context for when to use the tool: whenever installed Android packages need to be listed. It does not explicitly name alternatives or exclusions, but the sibling tools are clearly unrelated operations, so the intended use case is unambiguous.

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