meta_ads_creatives_create_carousel

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

With no annotations, description carries full burden. It discloses that the tool is mutating and reversible via rollback_apply, and notes return of creative id. Could mention permission requirements or side effects, but the information provided is sufficient for safe invocation.

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 sentences plus one for alternatives, front-loaded with the core action. No extra words; every sentence serves a purpose.

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 moderate complexity (5 params, nested cards, no output schema), description covers purpose, usage, and behavioral aspects. Lack of explicit error handling or prerequisites is minor; schema fills most 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 100%, so baseline is 3. Description adds value by explaining card structure and fallback behavior of main link. However, it does not elaborate on specific_parameter format beyond 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?

Clearly states it creates a Carousel AdCreative with 2-10 swipeable cards and returns the creative id. Explicitly distinguishes from sibling tools meta_ads_creatives_create_dynamic and meta_ads_creatives_create_collection by describing their alternative use cases.

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?

Provides explicit guidance on when to use this tool: 'useful for product catalogs or multi-step narratives.' Directly contrasts with dynamic (auto-optimized asset rotation) and collection (product-feed-driven) alternatives, helping the agent choose correctly.

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