install_app

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

With no annotations provided, the description carries the full burden for behavioral context. It only describes the basic action without disclosing potential side effects (e.g., overwriting existing installs), error handling, permissions required, or return behavior. This is insufficient for a safe agent invocation.

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 two concise sentences, immediately stating the core action and platform distinction. No filler or redundant information. It is well front-loaded.

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 lack of an output schema and the complexity of installing apps across platforms, the description omits critical context: prerequisites (e.g., device availability, app readiness), behavior when deviceId is omitted, error scenarios, and expected outcome (e.g., success indication). It is not complete enough for reliable agent operation.

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%, so the baseline is 3. The description adds minimal extra value by restating the app artifact types (APK, .app bundle), which is already detailed in the schema's parameter descriptions. No new semantic insights are provided.

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 clearly states the action (install an app) and the target (device or simulator), with platform-specific details (APK for Android, .app bundle for iOS). It effectively distinguishes from sibling tools like 'launch_app' (launches after install) and 'build_app' (builds before install).

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 provides no explicit guidance on when to use this tool versus alternatives, such as prerequisites (e.g., app must be built, device must be connected) or when not to use it. No mention of related tools like 'list_devices' to get device IDs.

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