create_multi_asset_ad

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

No annotations provided, so the description carries the full burden. It discloses key behaviors: enforced identity, asset modes, copy generation modes, Instagram gate, and blocking conditions. However, it does not mention return values or error handling, which would enhance transparency.

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 well-structured with sections and clear bullet points. It is fairly lengthy but each section adds necessary context. Could be slightly more concise by trimming redundant phrasing, but overall it's appropriately front-loaded and organized.

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 of 19 parameters and no output schema, the description covers modes, constraints, and conditional logic well. It lacks return value information and could mention error scenarios. Still, it provides sufficient context for an AI agent to understand usage.

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?

Input schema has 0% description coverage, so the description adds significant value. It explains the purpose and conditional requirements for many parameters (e.g., copy_mode, placement_mode, video/image hashes). Some parameters like account_id have minimal explanations, but overall it clarifies usage beyond 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 an ad with enforced identity, multi-asset support, and verification. It specifies two asset modes (VIDEO and STATIC IMAGE) with explicit conditions, distinguishing it from sibling tools like create_ad_creative (single image) and update_ad.

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?

The description provides explicit guidance on when to use each mode, what is blocked (mixed video+image, single image hash), and the Instagram gate via placement_mode. It also references the alternative tool create_ad_creative for single image cases.

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