create_ad

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

The description discloses that new ads default to PAUSED status, which is a useful behavioral trait. With no annotations provided, it does not mention potential side effects, required permissions, or error behavior, leaving some gaps in transparency.

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 three short sentences, front-loaded with the action ('Create a new ad'), and each sentence adds essential information (required params, creative format, default status). There is no fluff or redundancy, making it highly concise and well-structured.

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?

The description covers the essentials: purpose, required parameters, creative format, and default status. However, without an output schema, it omits any mention of the return value (e.g., created ad ID) and does not state prerequisites like ad set ownership or account context. This leaves some contextual gaps for a create tool.

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?

Since the input schema provides 100% description coverage for all parameters, the description only repeats the required fields and clarifies that creative is a JSON object_story_spec, which the schema already states. This adds no new meaning beyond the structured data, so the baseline score of 3 is appropriate.

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 a new ad' with a specific verb and resource, distinguishing it from sibling tools like get_ad, update_ad, and delete_ad. It also mentions the required parameters (name, adset_id, creative), which further disambiguates it from other create operations.

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 implies when to use this tool by requiring an adset_id, suggesting it should be used when creating an ad within an existing ad set. However, it does not explicitly state exclusions or alternative tools, so it lacks the explicit comparative guidance of a 5.

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