ozon_seller_action_create

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

With no annotations provided, the description carries the full behavioral burden, but it only restates the create intent. It does not disclose whether creation is immediate, whether the promotion starts in a draft or active state, what validation is applied to dates or discounts, or any side effects.

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 economical sentence and is easy to parse, with the core verb and resource up front. The Russian parenthetical adds minor redundancy but does not significantly hurt clarity.

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 mutating create operation with no annotations and no output schema, this one-sentence description is insufficient. It omits when to use it, what the required fields mean beyond partial schema hints, expected date formats for date_end, and the relationship to sibling activation/toggle tools.

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 description contributes no parameter-level information; title and date_end remain undefined in both the description and schema. Only two of four parameters have schema descriptions, and the description does not compensate for the missing ones.

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 uses a specific verb ('Create') and resource ('seller's own discount promotion'), making the function's objective unmistakable. It also includes the Russian equivalent, which disambiguates platform-specific terminology and separates this create operation from sibling list/activate/toggle 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?

No guidance is given for when to use this tool versus alternatives such as ozon_actions_activate, ozon_seller_action_toggle, or ozon_actions_list. It does not state prerequisites or whether a created promotion must later be activated.

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