Create Ad

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

The description adds minimal behavioral context beyond the annotations. Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds the requirement that a creative must pre-exist, which is useful, but it does not disclose potential side effects, validation behavior, or outcome on success. With annotations covering the basic safety profile, a score of 3 is appropriate.

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 a single, concise sentence that conveys the core purpose and the most important prerequisite. There is no wasted text, and the key information is front-loaded.

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 simple create tool with a fully described schema and useful annotations, the description is adequately complete. It covers the essential prerequisites and scope. It does not describe return values, but no output schema exists, and the tool's behavior is straightforward. Minor gap: it doesn't mention the status parameter or any default behavior, but the schema covers that.

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 100%, so the baseline is 3. The description repeats the prerequisite for creative_id that is already stated in the schema ('create with create_adcreative first'). It adds no new parameter semantics beyond what the schema provides, so it does not exceed the baseline.

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's purpose: 'Create a new ad within an ad set.' The verb 'create' and resource 'ad' are specific, and the context 'within an ad set' distinguishes it from siblings like create_campaign and create_adset. It also mentions key dependencies (adset_id and creative_id), leaving no ambiguity.

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 sequencing guidance: 'create the creative first with create_adcreative.' This clearly indicates when to use this tool relative to a sibling. It does not explicitly state when not to use it, but the prerequisite and purpose are sufficient for an AI agent to choose this tool appropriately.

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