[Write] Set the app to free

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

No annotations are provided, so the description carries full burden. It discloses that the price is scheduled (not immediate), that Apple automatically equalizes $0 across territories, that paid pricing is unsupported, and that dryRun is available. This is rich behavioral context beyond the schema.

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 sentences front-load the core action, then add limitations and dryRun support. The redundant 'Write.' prefix is minor but overall the description is immediately scannable and free of fluff.

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 simple write tool with no output schema, the description covers the action, territorial behavior, limitations, and dryRun. It stops short of explaining what the user should do after scheduling (e.g., verify with asc_pricing_get), leaving a slight gap in the full workflow context.

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% (appId, dryRun, baseTerritory are all described). The description adds a little extra context by explaining that scheduling occurs in the base territory and that dryRun is supported, but it does not significantly expand on parameter formats or constraints 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 the tool's purpose: sets the app's price to free by scheduling $0 in the base territory. It also specifies the resource (app pricing) and distinguishes from the sibling asc_pricing_get by focusing on the write action and explicitly noting that paid price points are not supported.

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 the tool (when you want the app free) and provides a key exclusion: paid price points are not supported. It also highlights dryRun support as a safe preview option. However, it does not explicitly name alternative tools for paid pricing or verification, so it's not a full 5.

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