Create Ad

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only restates that the tool creates an ad and lists some field constraints; it does not mention idempotency, permissions, side effects, or response behavior despite having an idempotency_key parameter.

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 sentences with no filler; the primary action is front-loaded and the creative-type details are compactly summarized. Every phrase earns its place.

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?

For a 10-parameter creation tool with no annotations and no output schema, the description plus schema is mostly adequate for invocation. However, it leaves idempotency semantics and response shape unaddressed, so the agent must infer important behavioral details.

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 90%, so the baseline is 3. The description adds helpful context linking creative_type to target_url and file_id for chat_card, but most of this duplicates the schema's existing parameter descriptions, and idempotency_key remains unexplained.

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?

States a specific verb and resource: 'Create an ad in an ad group', which clearly distinguishes it from sibling tools like create_ad_group or create_campaign. It also enumerates the two creative types, making the tool's exact scope explicit.

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?

Clearly indicates this is the tool for creating an individual ad within an ad group, and notes that product_ad_template is for product feed campaigns. It lacks explicit exclusions or comparisons to alternatives such as submit_bulk_mutation_job, but the context is clear.

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