meta_ads_creatives_create_dynamic

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

Despite no annotations, the description discloses key behavioral traits: mutation ('Mutating'), reversibility ('reversible via rollback_apply'), and runtime behavior ('Meta combines them at serve time'). It does not cover potential rate limits or specific error conditions, but provides sufficient context for safe usage.

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 concise yet packed with information: purpose, return value, behavioral notes, usage guidance, and sibling differentiation. Each sentence contributes uniquely, and the structure front-loads key facts.

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 the complexity of dynamic creatives and the absence of an output schema, the description covers all essential aspects: creation, return ID, mutability, reversibility, asset requirements, and placement-specific notes. No critical gaps are evident for an agent to operate correctly.

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 100% with descriptions for all 9 parameters, so baseline is 3. The description adds value by giving recommended ranges (2-10 images, 1-5 bodies, etc.) and clarifying optional fields like descriptions ('not all placements render these') and CTAs ('values drawn from same set').

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 defines the tool's purpose: 'Creates a Dynamic Creative' with Meta auto-generating combinations. It distinguishes from siblings by naming 'meta_ads_creatives_create' for static ads and 'meta_ads_creatives_create_carousel' for multi-card layouts, and explains the asset mix optimization.

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?

Explicitly states when to use: 'when you want Meta to learn the best-performing asset mix rather than testing manually.' Provides clear alternatives for static and multi-card ads, and gives specific asset counts (2-10 images, 1-5 text fields).

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