create_ad

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

No annotations provided, but the description discloses the default PAUSED status and the DCO-bypass pattern. However, it does not mention idempotency, permissions, or error behavior, which is partially compensated by the presence of an output schema.

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, no wasted words. The first sentence states the action, the second provides crucial workflow details and default. Highly concise and 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?

Given 5 parameters and no schema documentation, the description covers the unique DCO-bypass flow and default status. However, it does not explain how to obtain required params like 'adset_id' or 'account_id', or what the output contains, though an output schema is present.

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 0%, so the description must add meaning. It adds context for 'creative_id' (as PLACEHOLDER) and 'status' (default PAUSED), but other parameters (name, adset_id, account_id) lack explanation, leaving gaps for an agent.

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 states 'Create an ad.' with a clear verb and resource. It also specifies a unique workflow (DCO-bypass) and default status, distinguishing it from siblings like update_ad.

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?

Explicitly indicates when to use this tool: for the DCO-bypass flow, pass a PLACEHOLDER creative_id and then call update_ad. Also mentions the default PAUSED status, providing clear guidance on usage.

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