meta_ads_creatives_create_carousel

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

With no annotations provided, the description carries full responsibility. It discloses that the tool is mutating, not automatically reversible, and recommends recording before-state with mureo_state_action_log_append. It also mentions the return value (new creative id), which is critical behavioral information.

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?

Three sentences, each earning its place: purpose, mutability/rollback guidance, and alternatives. Front-loaded with the core action, then critical risks, then distinctions. No fluff or redundancy.

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 tool's moderate complexity and absence of output schema, the description is complete: it explains the return value, mutation risk, use cases, and alternatives. Combined with detailed input schema, an agent has enough context to select and invoke this tool 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%, so baseline is 3. The description adds value beyond schema by explaining that link is used for the 'See More card' and as fallback, and by describing the card structure (image/video, name, description, link). This enriches understanding of the parameters without duplicating schema details.

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 opens with 'Creates a Carousel AdCreative with 2–10 swipeable cards', giving a specific verb, resource, and format. It clearly distinguishes from sibling tools by naming meta_ads_creatives_create_dynamic and meta_ads_creatives_create_collection as alternatives for different 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?

Explicitly states when to use alternatives: 'For auto-optimized asset rotation use meta_ads_creatives_create_dynamic; for product-feed-driven carousels use meta_ads_creatives_create_collection.' Also provides context for when this tool is appropriate (product catalogs or multi-step narratives).

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