ozon_search_promo_enable

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the 1000-SKU cap and implies a paid promotion model, but it does not disclose side effects, whether the operation is idempotent, whether it replaces an existing promotion, or any authorization requirements.

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 that front-loads the action and key constraint. The parenthetical Russian phrase is slightly redundant but not harmful.

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 one-parameter tool, the description covers the core action, the target object, and an important limit, which is minimally viable. But given there are no annotations and no output schema, the absence of usage context and behavioral effects leaves the description incomplete for confident invocation.

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 describes skus as an integer array but nothing else. The description adds that the SKUs refer to 'goods' and imposes a 1000-SKU maximum, which adds meaning. However, with 0% schema coverage, it still does not clarify whether these are Ozon SKU IDs, seller SKUs, or other identifiers, so it only partially compensates.

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 specific verb ('Enable'), a specific resource ('pay-per-order promotion'), and a scope ('goods, max 1000 SKU'). This clearly distinguishes it from related siblings like ozon_search_promo_disable and ozon_search_promo_bids, even without naming them.

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 gives no guidance on when to use this tool versus alternatives such as ozon_search_promo_disable, ozon_search_promo_bids, or other promotion activation tools. It also omits prerequisites or conditions that should be checked before enabling.

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