create_dynamic_creative

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

No annotations provided. The description reveals the automatic combination behavior but omits details on permissions, side effects, or whether existing data is modified. Carries the full burden but is adequate.

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?

Two efficient sentences, front-loaded with purpose, no redundant 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?

Adequate for a simple create tool with two parameters and no output schema; could be improved by mentioning expected return value (e.g., creative ID).

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% and describes asset_feed_spec structure. The description adds meaning by explaining that Meta automatically combines provided components, which goes beyond schema content.

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 the tool creates a dynamic creative using asset_feed_spec, distinguishing it from other creative tools like create_creative by mentioning automatic combination of components for optimization.

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 explains that Meta automatically combines components for performance, implying use for A/B testing, but does not specify when not to use it or compare with alternatives like create_creative.

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