Upload Bundle

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the tool both uploads and commits, which is a significant side effect, and that it is disabled in read-only mode. It does not cover permissions or failure behavior, but the core behavioral traits are clearly surfaced.

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 short sentences with no filler. The primary action is front-loaded, and the read-only limitation is stated in a single appended sentence that earns its place.

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 has only two fully documented parameters and an output schema, so return values do not need explanation. The description makes the operation and its commit side effect clear, though it could more explicitly explain the edit lifecycle or contrast with similar bundle-upload 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?

The input schema already documents both parameters at 100% coverage. The description adds no new meaning beyond restating that the file is an .aab and that a package name is involved, so it provides the baseline value rather than compensating for schema gaps.

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 action: upload an Android App Bundle (.aab) to a new edit and commit it. This clearly distinguishes it from APK uploads (upload_apk), internal app sharing bundle uploads (upload_internal_app_sharing_bundle), and other upload variants.

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 '.aab' extension and 'new edit' language imply this is for production app bundle uploads that move through the edit lifecycle, but the description never explicitly says when to choose this over upload_internal_app_sharing_bundle or upload_apk. The read-only note is a constraint, not an alternative selector.

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