create_ad_creative

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

No annotations provided, so description carries full burden. It discloses special behavior for sponsored content and lead gen, but lacks details on side effects (e.g., does it modify the campaign?), permissions, or success feedback. The description mentions parameters not in schema (leadgenFormUrn, contentReference), which may confuse about expected 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 two sentences. The first sentence declares the main purpose, and the second provides essential subtype guidance. No redundancy, front-loaded with core action.

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 6 parameters, 2 required, enums, and no output schema, the description omits return values, prerequisites (campaign existence), and parameter relationships. It references missing parameters (leadgenFormUrn, contentReference) without explanation, leaving significant gaps for a tool of this 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?

Schema description coverage is 67% (missing descriptions for 'type' and 'callToAction'). The description adds some context by explaining 'callToAction' for lead gen and implying 'type' usage, but introduces parameters not in schema (leadgenFormUrn, contentReference) without clarity. This partially compensates for schema gaps but also misleads.

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 creative and associate it with a campaign', providing a specific verb and resource. It distinguishes from siblings like create_full_ad by focusing on creative-only creation with campaign association, and adds subtype guidelines for sponsored content and lead gen.

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 gives contextual advice for sponsored content and lead gen ads, specifying prerequisites (create share/post for sponsored content, provide leadgenFormUrn and callToAction for lead gen). However, it does not explicitly compare with sibling tools like create_full_ad or state when not to use this tool.

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