app_store_version_promotions__create

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

Annotations already signal that this is a non-read, potentially destructive operation (readOnlyHint=false, destructiveHint=true). The description adds the context that this is a 'RELEASE-level write', which provides some additional behavioral nuance, but it does not disclose side effects, prerequisites, or what specific state might be affected beyond what the annotation implies.

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 extremely concise and front-loaded: one sentence states the action, and one sentence gives the endpoint and risk level. Every word earns its place with no fluff or repetition.

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?

Despite the schema being rich, the description lacks any high-level context about what an App Store version promotion is, when it is needed, or what the operation's success criteria are. With no output schema and a complex nested request body, the description alone would leave an agent under-informed about the business purpose and end 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 for the 'body' parameter, including nested relationship details. The description itself adds no parameter-specific semantics, but the schema does the heavy lifting, so a baseline score of 3 is appropriate.

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 'Create an App Store version promotion', using a specific verb and resource. It does not explicitly distinguish from sibling tools, but the resource name is unique among the long sibling list, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. The phrase 'RELEASE-level write' hints at context but does not explain under what circumstances a promotion should be created, nor does it mention any exclusions or alternatives.

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