Create a beta app review submission by linking a build ID, sending the build to Apple for TestFlight beta review.
Create a beta app review submission. [POST /v1/betaAppReviewSubmissions] RELEASE-level write.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON:API request body (Apple schema: BetaAppReviewSubmissionCreateRequest). |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructive/write behavior (readOnlyHint=false, destructiveHint=true), so the description need not repeat that. It adds the endpoint and 'RELEASE-level' qualifier, providing some context but not deep behavioral detail.
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 a single sentence with no wasted words, including the endpoint for reference. It is appropriately sized and front-loaded.
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?
The description is too brief for a create operation with nested relationships and no output schema. It does not mention what the response contains, any preconditions, or clarify the meaning of 'RELEASE-level'.
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 has 100% description coverage, so the schema already documents the parameters. The description adds no extra meaning 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 clearly states the action ('Create') and the resource ('beta app review submission'), and includes the REST endpoint. This is specific enough to distinguish it from sibling list/get 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?
No guidance is provided on when to use this tool versus alternatives. The phrase 'RELEASE-level write' is ambiguous and does not explain prerequisites, context, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.