ads_campaign_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. It usefully discloses that the campaign 'starts in draft status', which is real behavioral context, but for a 12-param mutation tool it says nothing about permissions, what happens to nested metadata/tracking/targeting, or side effects.

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?

Two short sentences, front-loaded with the core action, with zero filler. The terseness is efficient, though arguably too thin for the tool's complexity.

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?

Given 12 parameters, nested objects, no output schema, and no annotations, the description is far too sparse to guide correct invocation. It omits budget field distinctions, targeting/metadata/tracking structure, and required-field semantics (name, objective).

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% and the description compensates almost not at all. Only project_id is obliquely referenced ('optionally inside a project'); the many fields (daily_budget vs budget_amount, currency, source, starts_at/ends_at, targeting, metadata, tracking, objective enum) are entirely undocumented.

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?

States a specific verb (Create) and resource (advertising campaign definition), plus the qualifier 'local' that hints at a distinction from platform-specific siblings. It does not explicitly name or contrast with siblings like ads_yandex_direct_create_campaign or ads_telegram_ads_api_create_ad, so the differentiation is only implicit.

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 explicit when-to-use or when-not guidance, and no named alternatives despite many sibling campaign-creation tools existing. 'Local' and 'optionally inside a project' give hints about context but nothing tells an agent when to pick this over ads_telegram_ads_api_create_ad or ads_yandex_direct_create_campaign.

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