meta_ads_creatives_create_carousel

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

Without annotations, the description carries the full burden. It declares the tool as mutating and reversible via rollback_apply, which is helpful. However, it lacks details on required permissions, rate limits, or side effects beyond creation. Still, the core behavioral traits are covered.

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?

Five concise, front-loaded sentences with no fluff. Each sentence provides essential information: main action, return value, mutability, card details, and sibling comparisons. Perfectly structured for quick comprehension.

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 (nested cards, multiple media types) and no output schema, the description is fairly complete. It covers return type, reversibility, and use cases. Could be improved by noting prerequisites like page_id and account_id, but those are in the schema. Overall sufficient for an agent to decide when to invoke.

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 context about card structure and use cases but does not significantly enhance understanding beyond the schema's parameter descriptions. It reinforces mutual exclusivity of media fields but doesn't add new semantic depth.

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 states it creates a Carousel AdCreative with 2-10 swipeable cards and returns the creative ID. It distinguishes itself from siblings by explicitly naming alternatives (dynamic and collection) and their 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 when-to-use: 'useful for product catalogs or multi-step narratives.' Lists alternatives for different scenarios (auto-optimized asset rotation, product-feed-driven carousels). Also notes mutability and reversibility via rollback_apply.

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