List Generated Apks

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

With no annotations, the description carries the behavioral burden. It discloses that the tool returns one entry per downloadable generated APK, lists the APK types covered, and explains how the download ID is meant to be used. It does not mention pagination, sorting, or permission requirements, but for a read-style list operation these are minor omissions.

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?

Two focused sentences with the core action front-loaded and the return-detail and workflow in the second. Every sentence earns its place, with no repetition, filler, or unnecessary context.

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 two-parameter list operation with an output schema, the description is nearly complete: it defines the input context, the output granularity, the APK types, and the next step. It only lacks explicit guidance on when not to use it or where to source the version_code from, but these are minor gaps.

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%, and the schema already documents package_name and version_code. The description reinforces that version_code refers to the app bundle version, but it adds no new parameter semantics beyond what the schema provides. The baseline of 3 is appropriate.

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 and resource: 'List the APKs Google Play generated from an app bundle version.' It clearly identifies the scope and output granularity, and the emphasis on generated APKs distinguishes it from related tools like list_apks. It also names the downstream consumer, download_generated_apk, which reinforces the tool's role.

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 gives clear context: use this tool when you need the downloadable APKs generated from a specific bundle version, and then pass the returned download ID to download_generated_apk. It does not explicitly name alternative tools to exclude, but the generated-from-bundle framing is enough to guide selection.

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