app_store_version_promotions_create_instance

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

No annotations are provided, so the description carries the full disclosure burden, and it delivers almost none. It implies a mutation via 'POST' but says nothing about required permissions, side effects, whether the promotion is immediately active, or what a successful response contains. For a write tool with zero annotation coverage this is a serious gap.

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?

It is short, but the path is stated twice in immediate succession ('POST /v1/appStoreVersionPromotions (POST /v1/appStoreVersionPromotions)'), which is wasted space in an already thin description. The remaining sentence is functional but the duplication undermines front-loading.

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?

For a mutation tool with no annotations and no output schema, the description should explain what is being created and what to expect. Instead it offers only an endpoint and a schema reference, leaving the agent unable to call it correctly with confidence about the payload's intent.

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%, and the single body parameter is already documented with its JSON:API envelope shape. The description's pointer to components.schemas.AppStoreVersionPromotionCreateRequest repeats what the schema already says, adding no new meaning. Baseline 3 applies when the schema does the work.

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 only restates the HTTP method and path (POST /v1/appStoreVersionPromotions), duplicating itself in parentheses. It never explains what an app store version promotion is or what creating one accomplishes, so the agent learns nothing beyond the endpoint name. It reads as a tautology of the tool name rather than a statement of purpose.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling create_instance tools. The agent is given no basis for choosing this tool over, say, app_store_version_phased_releases_create_instance or other promotion-adjacent endpoints.

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