List Apps

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

Describes default filtering behavior and content of each entry. With no annotations, the description fulfills the burden adequately, though could note if there are permissions or timeout considerations.

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?

Three sentences providing purpose, default behavior, optional parameter, and output content. No wasted words, front-loaded with primary function.

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?

Covers purpose, parameters, and output format despite no output schema. Could be slightly more complete by mentioning if the list is sorted or includes package names only.

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?

Both parameters are described in the input schema, and the description adds context about default behavior for include_system and the device_id implicitly. With 100% schema coverage, baseline is 3; the description adds value with behavior details.

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?

Clearly states it lists installed applications on a device, distinguishes default behavior (user-installed only) and notes optional inclusion of system apps. Differentiates from sibling tools like install_app, uninstall_app, and launch_app.

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?

Explains when to use the include_system parameter. However, no explicit mention of when not to use this tool or alternatives for other device-related queries.

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