meta_ads_ad_sets_create

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

No annotations provided, so the description carries the full burden. It discloses that the operation is mutating, reversible via rollback_apply (sets status to PAUSED), and that the default initial status is PAUSED, only becoming ACTIVE after operator confirmation. This provides good behavioral insight beyond the basic 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?

The description is concise, with two main sentences plus a few additional points. It is front-loaded with the primary action and return value, and every sentence adds value. No filler.

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 tool has 9 parameters, nested objects, and no output schema. The description covers creation, return value, reversibility, default status, and post-creation workflow. It doesn't detail every parameter, but the schema provides that. It is adequately complete for the 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 100%, so baseline is 3. The description adds value by summarizing targeting requirements ('at minimum supply geo_locations and age bounds') and clarifying the default status behavior. This goes beyond the schema's individual parameter documentation.

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 'Creates a new ad set inside an existing campaign. Returns the new ad_set id.' This clearly indicates the action (create), the resource (ad set), and the context (inside an existing campaign). It distinguishes from sibling tools like meta_ads_ad_sets_get, meta_ads_ad_sets_list, etc.

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 context: it indicates the tool is for creating ad sets, specifies that after creation one should attach ads with meta_ads_ads_create, and mentions default status behavior. However, it does not explicitly state when not to use this tool or list alternatives, but the context is clear enough.

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