List Apps

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

With no annotations at all, the description carries the full disclosure burden. It never states that this is a read-only, side-effect-free operation, what happens if no device is attached, or whether the device parameter defaults to the current target — all things an agent needs before invoking a device-level command.

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 short sentences, no filler, with the core purpose front-loaded and the filter behavior immediately after. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained. However, for a two-parameter tool with zero schema description coverage and no annotations, the unexplained `device` parameter leaves a real hole an agent must resolve by trial.

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%, so both parameters depend entirely on the description. The description handles third_party_only well (name, type, and effect), but the `device` parameter is never mentioned, leaving an agent to guess whether it takes a serial, an index, or an alias.

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 opens with a specific verb and resource: "List installed apps on the device," which is immediately distinguishable from list_devices and the launch/stop/uninstall siblings. It also carves out scope with the third_party_only filter. It stops short of naming a sibling or stating the resulting app-object shape, so it isn't 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?

There is useful guidance for choosing a parameter value ("Set third_party_only=True to skip pre-installed system apps"), which implies when to use each mode. But there is no guidance on when to call list_apps versus inspecting a package another way, and no mention of prerequisites such as a connected device.

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