meta_ads_creatives_create_collection

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

No annotations given, but description discloses mutation, reversibility via rollback_apply, and prerequisite catalog setup. Doesn't detail rate limits or auth scopes, but 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?

Three succinct sentences: first defines purpose/output, second notes mutability/reversibility, third provides prerequisite and alternative. No wasted words.

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 annotations or output schema, description covers purpose, usage, prerequisites, alternative, and parameter relationships. Leaves out error handling but complete enough for a creation 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?

With 100% schema coverage baseline is 3. Description adds value: mutual exclusivity of cover_image_hash/cover_video_id, page permission requirement, and product_ids source hint via meta_ads_products_list.

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 Collection AdCreative from a catalog into a mobile-optimized storefront layout, returns creative id, and distinguishes from sibling carousel tool.

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 says when to use (catalog-based collection), when not (static card decks), and provides prerequisite: setup catalog via meta_ads.catalogs.* tools.

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