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, reversible via rollback_apply, and returns the new creative id. Also mentions prerequisites and permission requirements. While it does not detail every side effect, it adequately informs the agent of key behavioral traits.

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 extremely concise with three sentences covering purpose, return/reversibility, prerequisites, and alternative. No unnecessary words; highly efficient.

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 no output schema and 7 parameters, the description provides enough context for typical usage: purpose, prerequisites, alternative, parameter details, and return value. It may lack error scenarios or rate limits, but these are acceptable gaps for a create tool.

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 description coverage is 100% with all parameters described. The description adds extra context beyond schema: account_id can fallback to env variable, page_id requires permission, product_ids can be listed via meta_ads_products_list, link requires HTTPS, and cover_image_hash and cover_video_id are mutually exclusive. This adds meaningful value.

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 that the tool creates a Collection AdCreative pulling products from a catalog into a mobile-optimized storefront layout. It distinguishes from the sibling tool meta_ads_creatives_create_carousel by specifying that this is for catalog-based collections, not 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 tells when to use: requires a Meta product catalog set up via meta_ads.catalogs.* tools. Also provides an alternative: use meta_ads_creatives_create_carousel for static card decks. Clear usage context.

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