List Apps

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

Annotations already mark this as readOnlyHint=true, so the description does not need to restate safety. The description adds no additional behavioral details such as output format, completeness guarantees, or potential limitations. There is no contradiction with annotations.

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 clear sentence with no filler or redundant phrasing. It conveys the complete functional scope of the tool efficiently.

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?

For a simple read-only tool with one documented required parameter and annotations declaring safety, the description is sufficiently complete. It could specify the output format, but the returned data is reasonably inferable from 'List all the installed apps.'

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 100%, and the schema already explains the device parameter and recommends mobile_list_available_devices. The tool description does not need to add parameter-level information, so the baseline of 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?

The description uses a specific verb ('List') and resource ('installed apps on the device'), which clearly distinguishes it from app-manipulation siblings like mobile_launch_app, mobile_terminate_app, mobile_install_app, and mobile_uninstall_app. It communicates exactly what the tool returns.

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 tool's intended use is obvious from 'List all the installed apps on the device.' The parameter description adds helpful context by pointing to mobile_list_available_devices for discovering device identifiers, though it does not explicitly state exclusions or when to prefer other listing tools.

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