create_system_apk_variant

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Disabled in read-only mode,' which is a mode restriction, not a detailed behavior of the action itself. No mention of side effects, permissions, or what happens after creation beyond the output schema.

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 exceptionally concise: two sentences with no fluff. Every word contributes to the purpose or a key restriction. It is efficiently front-loaded with the action and the read-only caveat.

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?

Despite having an output schema, the description offers little contextual completeness for a create operation with nested objects. It lacks workflow context (e.g., prerequisite of uploading the bundle), potential failure scenarios, or how this variant integrates with other actions. The read-only note is a small addition but insufficient for a complex mutation.

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 covers 100% of parameters with descriptions, including the nested `variant` object. The description adds no extra semantic meaning beyond what the schema already provides, so baseline 3 applies.

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: 'Create a system APK variant from an uploaded app bundle.' This is a specific verb+resource combination that distinguishes it from deployment or other creation tools like create_in_app_product. It also notes read-only mode restriction, adding context.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only mentions 'from an uploaded app bundle,' implying a prerequisite but without explicit instructions or exclusions. No mention of alternatives or conditions for use.

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