Create an App Store review attachment by providing file name and size, linked to a specific app store review detail.
Create an App Store review attachment. [POST /v1/appStoreReviewAttachments]
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON:API request body (Apple schema: AppStoreReviewAttachmentCreateRequest). |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what annotations already reveal (non-read, non-idempotent, non-destructive). No side effects or authorization needs are disclosed.
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 very concise with one sentence and an endpoint. It is front-loaded and efficient, though it could include more context without being verbose.
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 nested schema and lack of output schema, the description is incomplete. It fails to mention the prerequisite relationship with appStoreReviewDetail or the expected result.
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 description does not need to add parameter details. Baseline score of 3 is appropriate as the description adds no additional semantic information.
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 verb 'Create' and the resource 'App Store review attachment', which is distinct from sibling tools like delete, get, and update.
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. Prerequisites, such as the need for an existing appStoreReviewDetail, are not mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.