native_run_install_app

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

With no annotations, the description carries full burden but only states the basic function. It doesn't disclose behavioral traits such as required permissions, whether installation is destructive, error handling, or output format. This leaves significant gaps for a tool that performs device-level operations.

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, efficient sentence with no wasted words. It front-loads the core purpose ('Install app on device') and adds necessary technical context ('using native-run') and scope ('works for Android APK & iOS app').

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 tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks details on parameter usage, behavioral expectations, error cases, and output, making it incomplete for safe and effective agent invocation.

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 description adds minimal semantics beyond the schema: it implies 'appPath' is for Android APK or iOS app files, and 'platform' selects between them. However, with 0% schema description coverage, it doesn't fully compensate for undocumented parameters like 'deviceId' or provide format details for 'appPath'.

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 app') and target ('on device'), specifying it uses 'native-run' and works for both Android APK and iOS app. It distinguishes from siblings like 'android_install_apk' by mentioning cross-platform capability, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives like 'android_install_apk' or 'ios_boot_simulator'. The description mentions it works for both platforms, but doesn't specify scenarios, prerequisites, or exclusions for its use.

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