create_multi_asset_ad

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

Despite no annotations, the description discloses important behaviors: enforced identity, support for two asset modes, blocking of mixed video+image, and placement mode effects (full_meta requires Instagram identity and blocks if unavailable). However, it does not mention output format or error behavior.

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, bullet points, and lists, and front-loads the purpose. It is thorough but concise given the complexity; a minor redundancy exists (repeating 'not mixed' twice).

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?

The description covers core logic (asset modes, placement, copy modes) and parameter details, addressing Instagram gate and copy generation modes. It lacks information on return value or error handling, but the absence of an output schema makes this acceptable. Overall, it is complete for the tool's complexity.

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 schema description coverage at 0%, the description compensates fully by explaining each parameter's purpose, default values, and constraints (e.g., copy_mode options, placement_mode options, conditions for video vs image hashes). This adds significant meaning beyond the schema's titles.

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 'Create an ad with enforced identity, multi-asset support, and verification' and distinguishes itself from sibling 'create_ad_creative' by noting that single image hash should use that tool instead. It explicitly defines two asset modes (VIDEO and STATIC IMAGE) and their conditions.

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 this tool (e.g., for multi-asset ads or single video) and when to use an alternative (single image hash should use create_ad_creative). It also details placement modes and their implications for Instagram identity requirements.

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