List Bundles

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

With no annotations, the description carries the burden of disclosing behavior. 'List ... currently uploaded' indicates a read-style enumeration and scopes it to existing uploads, but it does not mention pagination, ordering, permissions, or other operational characteristics. The output schema covers return structure, so some burden is reduced, but behavioral caveats are absent.

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?

A single sentence that front-loads the action and resource. There is no filler or repetition, and every word contributes to the meaning.

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?

This is a simple one-parameter list operation with an output schema available. The description accurately captures what the tool does, the input schema documents the only parameter, and the output schema covers return values. Nothing essential is missing for correct invocation.

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 schema already describes package_name as 'App package name' with 100% coverage. The description adds no additional parameter-level meaning, such as expected format or validation rules, so it is at the baseline for fully documented schemas.

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 ('List'), a precise resource ('Android App Bundles'), and a scope ('for an app'). It is immediately distinguishable from sibling tools like list_apks and list_generated_apks because the resource type is explicit.

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 'currently uploaded' gives clear context that this is for retrieving existing bundle uploads, but it does not explicitly say when to prefer this tool over alternatives such as list_apks or list_generated_apks. Usage guidance is implied rather than stated.

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