wb_advert_start

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. Starting an ad campaign is a state-changing action with financial implications (budget spending begins), yet the description discloses no side effects, reversibility, or state requirements. It simply states the transition without its consequences.

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 efficient sentence with the core action front-loaded. The Russian parenthetical 'запустить рекламу' adds marginal value for non-English agents but is essentially redundant with the English text.

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?

Despite low structural complexity (one parameter, no output schema), the tool activates advertising spend and belongs to a state-transition lifecycle. The description omits prerequisites (is the campaign required to be paused or newly created?), side effects (spending begins), and return behavior — gaps that matter for a financially impactful action.

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%, so the description must compensate, but it does not mention advert_id at all. The parameter name is self-explanatory enough that the gap is not severe, but the description adds zero meaning beyond the schema.

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 action ('Start') on a clear resource ('an ad campaign'), and the Russian gloss reinforces the meaning. It differentiates from lifecycle siblings like wb_advert_pause, wb_advert_stop, and wb_advert_delete via the distinct 'start' verb. However, it does not clarify whether 'start' is for newly created campaigns only or also resumes paused ones, leaving some ambiguity against wb_advert_create.

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 the many ad-lifecycle siblings such as wb_advert_create, wb_advert_pause, wb_advert_stop, or wb_advert_delete. No prerequisites (e.g., campaign must exist or be paused) or conditions for use are mentioned.

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