[Write] Attach a build to an App Store version

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

No annotations are provided, so the description carries the burden. It discloses the core action (sets the shipping build) and the dryRun preview capability. However, it doesn't mention whether the previous build selection is overwritten, requires a specific version state, or any error conditions.

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?

The description is short and front-loaded with the action, but the initial 'Write.' is redundant with the title. The two substantive sentences are efficient and contain the essential 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?

Given the moderate complexity and no output schema, the description covers the core purpose but lacks information about return values, side effects, or interplay with the version lifecycle (e.g., validation before submission). However, the schema covers parameters, so the description is adequate but not complete.

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 provides full descriptions for all four parameters (100% coverage), so the baseline is 3. The tool description only repeats the dryRun concept already in the schema, adding no extra parameter meaning.

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 the tool's function with a specific verb ('Sets') and resource ('which uploaded build an App Store version will ship'), distinguishing it from siblings like asc_version_update or asc_build_upload. The title further confirms 'Attach a build to an App Store version.'

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 the tool is used when you need to set the build for an App Store version, but it doesn't explicitly state when to use it over alternatives or mention any exclusions. It only mentions dryRun for previewing, which is more of a parameter feature than usage context.

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