wb_advert_create

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 discloses the campaign type and bid_type options, but does not mention side effects, prerequisites, whether creation auto-starts, billing implications, or what the response contains. For a mutating create operation, this is a significant transparency gap.

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 short and front-loaded with the core purpose. However, the trailing Russian phrase '(создать кампанию)' is redundant and does not add information beyond 'Create ad campaign', so it does not fully earn 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?

With five parameters, no annotations, no output schema, and many related advert siblings, the description is incomplete. It explains neither expected return values, failure modes, prerequisites like balance or permissions, nor how this creation step interacts with other lifecycle tools.

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 coverage is high at 80%, so the schema already documents most parameters. The description adds a relationship between bid_type and placement_types, but this is largely restating the schema's own 'for manual: search, recommendations' note. Name remains undocumented in both schema and description, though it is required.

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 clearly states 'Create ad campaign' and adds a specific campaign type ('type 9 Search+Catalog, the only one since 2026'), making the tool's purpose specific and distinct from sibling tools like wb_advert_list, wb_advert_start, or wb_advert_delete. The verb and resource are explicit and unambiguous.

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 description implies use for creating a campaign and notes the campaign type is the only one since 2026, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. Usage context is only implied, with no direct guidance about sibling tools such as wb_advert_start or wb_advert_pause.

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