ozon_ad_campaign_activate

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. 'Start' implies a state-changing mutation, but it does not mention preconditions, side effects such as spending resumption, reversibility, or idempotency.

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 short sentence with a clarifying translation, containing no filler. It is appropriately concise for the limited content, though that content is thin.

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 mutation tool with no annotations and no output schema, this description is incomplete. It lacks information about required campaign state, what activation does, and what the caller should expect in return.

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. The tool description does not explain what campaign_id refers to or how to obtain it, leaving the parameter's meaning almost entirely implicit.

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 'Start an ad campaign' uses a specific verb and resource, and the Russian 'запустить кампанию' reinforces the action. It is clear enough to distinguish from create/stop siblings in intent, though it does not explicitly say it activates an existing campaign rather than creating one.

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 guidance on when to use this tool versus alternatives like ozon_ad_campaign_create or ozon_ad_campaign_stop. The description gives no context for choosing this tool over its siblings.

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