device_list_apps

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does communicate an important scope constraint by saying 'user-installed' rather than all apps, and implies a read-only listing operation. However, it does not disclose how the udid selects a device, what happens if multiple devices are connected, or whether system apps are excluded beyond the qualifier.

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 one short, front-loaded sentence with no filler or repeated information. It earns its place by adding the 'user-installed' scope and device target without unnecessary detail.

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 with a single optional parameter and an output schema, so the missing return-value detail is less critical. However, the complete absence of parameter semantics and sibling routing leaves the description only minimally viable for an agent deciding how to invoke it.

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% and the description never mentions the only parameter, udid. The agent gets no explanation of what udid is for, whether it defaults to a single connected device, or how it affects the result list. This is a complete gap for the sole parameter.

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 action and resource: 'List user-installed apps on the connected device.' It clearly identifies the tool as an app-enumeration operation and distinguishes it from nearby device tools like device_list or device_info, though it does not explicitly name any sibling alternatives.

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 guidance on when to use this tool versus alternatives such as device_list, device_info, or device_install_app. The description does not mention prerequisites, device connection requirements, or any conditions that would make another tool more appropriate.

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