install_apk

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

With no annotations, the description carries the full burden for behavioral disclosure. It explicitly warns to install only from reliable sources, states that unknown-origin files trigger server confirmation, and notes the ADMIN prerequisite. These are meaningful behavioral traits beyond the schema, though it does not describe side effects like overwriting an existing app or how reinstall affects data.

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 short sentences, all substantive: the main verb and object appear first, followed by a critical path clarification, then safety and prerequisite notes. No filler or redundancy.

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 3-parameter mutable operation with no annotations and 0% schema coverage, the description covers the most important parameter and safety preconditions, but omits explanations for serial and reinstall and does not mention what constitutes a successful install. Since an output schema exists, return values need not be described, but the parameter gaps make the definition only partially complete.

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 0%, so the description must compensate. It does meaningfully clarify local_path as a host-side path, which is the key ambiguity. However, serial and reinstall are left unexplained; their semantics must be inferred from names/types, and reinstall's behavior (e.g., replace vs. update, data preservation) is not described.

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 states a clear verb+resource: 'APK telepitese' (install APK) from computer to device via adb install. This unambiguously distinguishes it from sibling app-management tools like launch_app, stop_app, uninstall_app, and clear_app_data, none of which handle installation.

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?

It provides useful context by clarifying that local_path refers to a file on the computer, not the device, and by noting that ADMIN mode is required. However, it does not explicitly name alternatives or state conditions when not to use this tool, though no sibling appears to duplicate the install capability.

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