upload_build_to_asc

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but description adds crucial behavior: 'Returns immediately once the upload commits — does NOT wait for Apple's processing pipeline.' This adds value beyond annotations. Could include more details on failure/retry logic but still strong.

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?

Three sentences: purpose, immediate return behavior, and follow-up steps. No wasted words; highly efficient and front-loaded with key information.

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 tool with two simple parameters and no output schema, the description fully covers the return behavior and the necessary post-call actions (polling and subsequent call). It leaves no ambiguity about the workflow.

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 100% with descriptions for both parameters. The description adds context by specifying that app_id comes from list_asc_apps and ipa_url from a Codemagic build artifact, enhancing understanding beyond the schema.

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 clearly states 'Download an IPA from a Codemagic artifact URL and upload it to App Store Connect,' specifying the verb (upload) and resource (App Store Connect). It distinguishes itself from sibling tools like submit_for_app_store_review by explaining its immediate return behavior.

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?

Explicitly provides a complete workflow: after calling this tool, poll list_asc_builds until processingState is VALID, then call submit_for_app_store_review. It also implies when not to use (if synchronous completion needed).

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