ozon_pricing_strategy_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the destructive nature ('Delete'). It does not mention irreversibility, side effects on associated products or active strategies, or error behavior for nonexistent IDs.

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 very short and front-loaded with the key action. The Russian parenthetical 'удалить стратегию' is redundant for an AI agent but not harmful; it adds minor verbosity without semantic value.

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 destructive operation with no annotations and no output schema, the description is too minimal. It omits what happens after deletion, whether deletion is reversible, and any conditions or side effects the agent should warn the user about.

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 has 0% description coverage for strategy_id, and the description does not explicitly explain the parameter. However, 'a pricing strategy' combined with the parameter name 'strategy_id' makes the intended meaning reasonably inferable, though no source or format guidance is provided.

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 ('Delete') and resource ('a pricing strategy'), making the operation unambiguous. It clearly distinguishes from sibling tools like ozon_pricing_strategy_create, _update, _list, and _info.

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 about when to use this tool versus alternatives, nor any prerequisites such as whether the strategy must exist or be inactive before deletion. The usage context is entirely implied by the tool name and description.

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