Create System Apk Variant

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

With no annotations provided, the description adds some useful behavioral context: the operation is disabled in read-only mode, which signals that this is a mutating action. It also states dependency on an uploaded app bundle. However, it does not disclose potential side effects, permission requirements, or whether existing variants are affected.

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 short, front-loaded sentences with no filler. The core action and source are stated first, and the operational restriction is a brief, useful addition.

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?

The output schema exists, so return-value documentation is not required, but the description leaves important operational context unstated. It does not explain what a system APK variant is, how the variant body should be structured, or whether a prior upload bundle or edit is required. For a create-style mutation tool with no annotations, this is a meaningful completeness gap.

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 schema already documents the three parameters. The description adds no additional parameter-level detail beyond what the schema provides, which matches the baseline for fully covered parameter documentation.

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 specific verb and resource — 'Create a system APK variant' — and identifies the input source ('from an uploaded app bundle'). This clearly distinguishes it from related sibling tools like get_system_apk_variant, list_system_apk_variants, and download_system_apk_variant.

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 phrase 'from an uploaded app bundle' implies the prerequisite, and the verb 'Create' implies when the tool is appropriate. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives, only the generic read-only-mode restriction.

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