[Write] Sync .appstore/ SSOT config to App Store Connect

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

With no annotations, the description carries the full burden and does an excellent job: it discloses the diffing behavior ('unchanged fields are never re-written'), failure isolation ('One category failing doesn't stop the others'), exclusions, and dryRun support. This gives the agent a complete picture of side effects and safety without annotations.

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, no filler. The first sentence front-loads the verb, resource, and scope; the second explains diffing and failure tolerance; the third covers exclusions and dryRun. Every sentence adds distinct value.

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 complex sync tool with no output schema, the description covers the key behavioral aspects, scope, exclusions, and dryRun. It does not detail the exact return/report format, but it does say categories are 'reported separately' and dryRun 'preview[s] every change,' which is reasonably complete for selection and invocation.

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%, so the baseline is 3. The description adds some context about projectRoot (reads .appstore/appstore.yml) and mentions dryRun preview, but the schema already documents parameter meanings. No significant extra syntax or usage detail beyond what the schema provides.

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 opens with 'Write' and clearly states it reads .appstore/appstore.yml and syncs a specific set of categories (App Info, version metadata, availability, age rating, review info, pricing, content rights) to App Store Connect. This distinguishes it from the many sibling get/update tools by framing it as a bulk SSOT-driven sync, not a single-resource mutation.

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?

It provides clear context: use when you want to sync from a local SSOT config, and it explicitly calls out that screenshots and App Privacy are not covered. However, it does not name alternative sibling tools (e.g., asc_screenshot_upload) for those excluded actions, so it stops short of explicit when-not/alternative guidance.

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