list_bundles

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

With no annotations, the description carries the transparency burden. 'Currently uploaded' adds a small behavioral nuance (does not include in-progress uploads), but it does not mention read-only status, permissions, or other side effects. The verb 'List' implies non-destructive behavior.

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, clear sentence with no filler. Every word earns its place, and the front-loaded verb immediately communicates the action.

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 tool is simple with one parameter and an output schema, so the description is nearly sufficient. However, it could briefly note whether the list includes all bundle variants or just the latest, but 'currently uploaded' provides adequate context for most use cases.

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% for package_name, so the schema already documents the parameter. The description adds no extra parameter semantics beyond what is already in the schema, which is acceptable per baseline.

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 ('Android App Bundles') with clear scope ('currently uploaded for an app'). It distinguishes from sibling tools like list_apks by explicitly naming the artifact type.

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 when to use it (when you need to see uploaded bundles) but does not explicitly mention alternatives or exclusions. No guidance is given on when not to use this tool versus related list operations like list_apks.

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