ozon_ad_campaign_stop

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 communicates a high-level state change and urgency, but does not disclose whether the stop is reversible, what happens to the campaign's ads or budget, or what the response indicates.

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 front-loaded sentence with no filler: 'Emergency' signals urgency, 'stop of an ad campaign' states the action, and the Russian gloss adds useful context for the target audience. Every part earns its place.

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 with no annotations and no output schema, this is minimal but workable: the agent understands what action to take and which parameter is required. However, it lacks information about return values, reversibility, and side effects, which an agent may need 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 has one required integer parameter, campaign_id, with 0% description coverage, and the description does not mention this parameter at all. The parameter name is self-explanatory, but the description adds no guidance about how campaign_id is used or what values are expected.

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 and resource: 'Emergency stop of an ad campaign.' This clearly distinguishes the tool from siblings like ozon_ad_campaign_activate and ozon_ad_campaign_create, and the '[P0]' tag reinforces its role as a priority action.

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 'Emergency' qualifier implies when the tool should be used, but there is no explicit guidance about when it should be preferred over alternatives such as budget updates or pausing mechanisms. The usage context is implied rather than stated.

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