meta_ads_creatives_create_collection

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

No annotations provided, so description carries full burden. It discloses that the tool is mutating and reversible via rollback_apply. It notes the return of the creative id. Lacks details on permission requirements or rate limits, but as a create tool, the mutation is expected.

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?

Four sentences, each serving a clear purpose: purpose, return/mutation, prerequisites/alternative, and sibling differentiation. No wasted words. Key information is front-loaded.

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?

With 100% schema coverage and no output schema, the description fully explains the tool's purpose, prerequisites, return value, and relationship to alternatives. No gaps for an agent to misuse it.

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%, but description adds value by explaining that product_ids must be from a linked catalog and suggests listing via meta_ads_products_list. It also clarifies mutual exclusivity of cover_image_hash and cover_video_id, which is not 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?

The description clearly states it creates a Collection AdCreative that pulls products from a catalog into a mobile-optimized storefront layout. It specifies the return value (new creative id) and distinguishes from the sibling tool meta_ads_creatives_create_carousel for static card decks.

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 (catalog-based collections) and when not (for static card decks, use carousel). Provides prerequisite of setting up a Meta product catalog via meta_ads.catalogs.* tools. 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.