Install App

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

The description adds no behavioral context beyond what the annotations already provide. Annotations show readOnlyHint=false and destructiveHint=false, meaning this is a state-changing but non-destructive operation; the description does not mention potential side effects like overwriting existing apps, permission requirements, or what happens on failure.

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, direct sentence with no filler words, making it appropriately concise. It is front-loaded with the action, though it borders on restating the tool title.

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?

Given the two fully documented parameters and the absence of an output schema, the description is minimally sufficient for an agent to invoke the tool. However, it leaves gaps around return behavior, side effects, and the need for a valid installed-file path, which are not covered elsewhere except partially in parameter descriptions.

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?

The input schema already provides 100% parameter coverage, including detailed descriptions for both 'path' and 'device', so the baseline is 3. The description itself adds no extra parameter semantics beyond restating that an app is installed.

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 the specific verb 'Install' with the resource 'an app on mobile device', clearly distinguishing it from siblings like mobile_uninstall_app, mobile_launch_app, and mobile_terminate_app. It directly states the operation and scope without ambiguity.

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 description gives no guidance about when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The schema hints at using mobile_list_available_devices to find devices, but this is in a parameter description, not in the tool description, and no alternatives are named.

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