Create Ad

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate a non-read-only, non-idempotent operation; the description adds that it creates a new ad within an ad set, defaults status to PAUSED, and returns the new ad ID. It does not discuss auth or failure modes, but annotation coverage lowers that burden.

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?

One-line summary plus a compact Args block and return statement. Every line adds operational value; no filler.

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 create operation with no output schema, it states the return value, required inputs, and default status. It leaves response_format to the schema and does not mention alternate sibling tools, but those are minor gaps.

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 only 33%, yet the Args list compensates by explaining adset_id as 'Parent ad set ID', providing provenance for creative_id, and stating status enum/default. It omits response_format, but that parameter is already well-described in 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?

States 'Creates a new ad within an ad set' — a specific verb, resource, and containment scope. This clearly distinguishes it from siblings like meta_update_ad, meta_list_ads, and meta_delete_ad.

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?

Implies its use for new-ad creation rather than modification or listing, but never explicitly contrasts with meta_update_ad or meta_list_ads. The only routing hint is 'creative_id ... from meta_list_ad_creatives or meta_create_ad_creative', which helps with prerequisites, not tool selection.

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