Create app store version

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not idempotent or destructive. The description adds that it creates a version and optionally attaches a build, but does not disclose side effects, prerequisites, or response behavior. While it does not contradict annotations, the added behavioral context is minimal beyond the name and 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?

The description is two concise sentences, front-loaded with the core action and resource, followed by the optional attachment detail. Every phrase adds value; there is no 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 the tool's moderate complexity (6 params, 3 required, 2 enums, no output schema) and robust annotations/schema, the description adequately covers the essential purpose and key option. It does not explain return values or prerequisites, but the schema fills parameter details and annotations cover safety. A slightly richer description could have mentioned expected outcomes, but current completeness is strong enough for effective 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 description coverage is 100%, so parameters are already well-documented. The description highlights 'platform + version string' and 'Optionally attach a build', mapping to platform, versionString, and buildId, but adds no new meaning beyond the schema. The baseline of 3 applies due to high schema coverage.

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 action: 'Create a new App Store version', specifies the resource ('an app'), and provides key qualifiers ('platform + version string', 'Optionally attach a build'). This distinguishes it from siblings like get/update/list app store versions and other create-* tools.

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 usage—when you need to create a new App Store version—but gives no explicit guidance on when not to use it or alternatives. Sibling tools like update-app-store-version exist, yet the description does not contrast with them. This is an implied usage rather than explicit guidance.

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