[Write] Update App Store availability

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

With no annotations provided, the description carries the burden and discloses key behaviors: full replacement (destructive), live fetch for 'ALL', rejection of unknown codes before changes, and dryRun preview. This goes beyond basic mutation disclosure and helps the agent anticipate side effects.

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?

Four succinct sentences, front-loaded with 'Write' and the core action. Every sentence provides essential information without redundancy or filler.

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 no annotations and no output schema, the description adequately covers the tool's destructive nature, input constraints, validation behavior, and preview capability. It is complete for an agent to safely invoke the tool and interpret its effects.

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 parameter descriptions, but the description adds significant value by explaining territory code formats, the 'ALL' expansion behavior, unknown-code rejection, and dryRun's purpose—information not in 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 uses a specific verb ('Replaces') and resource ('full set of territories an app is available in'), clearly distinguishing it from sibling tools like asc_availability_get. The leading 'Write' label also signals the operation 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?

Clear context that this is a full replacement operation, with guidance on territory codes and the 'ALL' literal. It does not explicitly name alternatives or exclusions, but the sibling list includes a read counterpart, making the usage context sufficiently clear.

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