ozon_ad_campaigns

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 disclosing behavior. It adds useful micro-ruble conversion and enum values, but does not state whether this is a read-only retrieval, what the response contains, whether pagination applies, or how the view parameter changes behavior beyond the schema note.

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 compact and dense—one line covers budgeting units and the key enums without wasted words. However, it is somewhat cryptic and lacks the explicit operation statement that would make it a model of concise clarity.

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 no annotations and no output schema, the description must do more to orient the agent. It does not confirm the operation type, return semantics, or how the optional filters combine, so an agent would need to rely heavily on sibling names and inference.

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 100%, so the baseline is 3. The description adds value by defining the allowed adv_object_type values, the state enum values, and explaining the micro-ruble unit, all of which are missing from the parameter schemas.

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 identifies the resource (ad campaigns) and adds useful context about budgets, statuses, and filter enums, but it never states the operation with a verb like 'list' or 'get'. 'Ad campaigns' is a noun phrase, so an agent must infer from the tool name and siblings that this is likely a read/list tool.

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 about when to use this tool versus the many sibling ad-campaign tools, such as ozon_ad_campaign_stop, ozon_ad_campaign_budget, or ozon_ad_statistics. The description provides domain enums but no explicit 'use this when...' or 'alternatives...' context.

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