Delete an App Store version experiment treatment by ID to permanently remove it from the test.
Delete an App Store version experiment treatment. [DELETE /v1/appStoreVersionExperimentTreatments/{id}]
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID from the matching list call. |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / id / descriptionAdded value: +"ID from the matching list call."v2.0.0Input schema / properties / id / descriptionRemoved value: -"Resource identifier."v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true and idempotentHint=true, and the description adds no extra context beyond repeating 'Delete'. It doesn't disclose consequences like irreversibility or effects on related resources.
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 concise sentence with the endpoint, front-loaded and zero waste. Every word earns its place.
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 simplicity (one parameter, no output schema) and strong annotations covering destructive/idempotent behavior, the description is complete enough. It could mention success/failure responses but that's not critical for this minimal delete operation.
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% with a single 'id' parameter described as 'ID from the matching list call.' The tool description adds no additional parameter meaning, but the schema is sufficient.
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 explicitly states 'Delete an App Store version experiment treatment' with a specific verb and resource, clearly distinguishing it from sibling create/get/update variants. The endpoint is also provided for precision.
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 delete action is clear, but the description does not explicitly state when to use it versus alternatives or mention any prerequisites like listing first. The usage is implied by the operation type and tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.