generated_apks_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action but does not mention whether the operation is read-only, idempotent, requires special permissions, or returns any specific data structure. The agent must infer safety and behavior from the tool name alone.

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 sentence of 10 words, front-loaded with the action and key parameter. Every word is meaningful, and there is no redundancy. It is appropriately sized for the tool's simplicity.

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 simple list operation with 2 params and no output schema, the description is adequate but not fully complete. It tells what the tool does and the required input, but does not explain response format, pagination, or limitations. An agent might still need to infer details from the tool name or sibling tools.

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 coverage is 50% (packageName described, versionCode not). The description adds no new parameter meaning beyond the schema; it only mentions 'versionCode' in context but doesn't clarify its purpose or format. For a 2-param tool with incomplete schema, more elaboration is needed.

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 uses a specific verb ('List') and resource ('generated (split + standalone) APKs') and ties it to a specific input ('for a given bundle versionCode'). This clearly distinguishes it from sibling tools like 'apks_list' (which lists all APKs) and 'bundles_list'.

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 implies the usage context: when you have a bundle versionCode and need to see its generated APKs. It provides clear context but does not explicitly mention when to avoid using it or compare with alternatives like apks_list. However, the purpose is distinct enough that an agent can infer appropriate usage.

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