list_adb_packages

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

The annotations declare readOnlyHint=false, but the description explicitly ends with 'Read-only.' This is a direct contradiction that could mislead an agent about whether the call mutates state. Beyond that conflict, the description adds little behavioral context.

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?

Two tight sentences with the operation and scope front-loaded and the device-path caveat given prominence. Nothing extraneous.

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?

With no output schema, the description usefully explains the return shape (per-base-APK device paths) and clarifies they are device-side paths. The only gap is the contradictory read-only claim, which undermines completeness of the behavioral picture.

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 serial, scope enum, and analysis_project_id are already fully documented. The description reinforces the scope concept but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 packages') and adds scope ('one device', 'each base APK's device path'), which an agent can act on. It does not explicitly distinguish itself from sibling resolve_adb_packages or inspect_adb_package, leaving the agent to infer the difference.

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 word 'optionally scoped' and the note that paths are 'device filesystem paths, not host-local' imply when the tool is useful, but there is no explicit when-to-use versus resolve_adb_packages or inspect_adb_package, and no prerequisites beyond the required serial.

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