ozon_ad_products_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the mutation ('Remove goods') but does not say whether the removal is permanent, idempotent, reversible, or what consequences it has on the campaign.

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, which is appropriate for a simple delete tool. The Russian parenthetical is mildly redundant, but it does not add meaningful bloat or hidden structure.

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?

The core operation is clear enough for an agent to know this tool removes products from a campaign. However, with no annotations, no output schema, and no parameter guidance, the agent is left to infer the exact effect and return behavior. Adequate but with clear gaps.

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 0%, and the description does not explain campaign_id or skus beyond the generic terms 'campaign' and 'goods.' The schema property names and types provide some meaning, but the description adds no parameter-level detail.

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 verb and resource: 'Remove goods from a campaign.' This makes the core operation obvious and distinguishes it from sibling tools like ozon_ad_products_add. It does not explicitly mention 'ad campaign,' but the tool name and sibling context supply that detail.

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 explicit guidance about when to use this tool versus alternatives such as ozon_ad_products_add or ozon_ad_campaign_products. The only inferred usage is from the verb 'Remove,' but no conditions, prerequisites, or exclusions are stated.

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