wb_promotion_exit

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool does not call a promotion-exit API but instead restores prices/discounts via the Prices API, which is important and non-obvious. However, it does not clarify side effects, completion behavior, or whether prices are applied immediately, leaving some transparency gaps for a mutating operation.

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 one compact sentence that front-loads the action and includes the critical caveat about the missing exit endpoint. There is no filler or redundant repetition of the tool name.

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 single-parameter tool with full schema coverage of the parameter, the description provides enough context to understand the operation's purpose and mechanism. The absence of an output schema is acceptable since the tool does not promise a return value; however, a bit more detail on expected value formats or effects would make it fully complete.

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 schema already documents the only parameter and describes the expected array shape as '[{nmID, price, discount}] pre-promo values'. The tool description reinforces that these values are used to restore price and discount, which is consistent but adds little beyond the schema.

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 states a clear, specific action ('Leave a promotion') and the resource/mechanism ('restore price and discount via Prices API'). It also explains the unique context that WB has no exit endpoint, which effectively distinguishes this tool from the many sibling promotion and pricing 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?

The description implies the correct usage: when you need to exit a promotion, use this workaround because no dedicated exit endpoint exists. It gives clear context for when this tool is appropriate, though it does not explicitly list alternative tools or state 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.