meta_ads_ads_create

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

With no annotations provided, the description fully covers behavioral traits: it is mutating, reversible via rollback_apply, defaults to PAUSED status, and requires an existing creative. It also discloses the return value (new ad id).

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 two sentences long with no wasted words. Each sentence serves a purpose: overview, dependency, behavioral details. It is front-loaded with the primary action.

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 output schema, the description covers all critical aspects: tool action, input requirements, dependencies (creative must exist), initial status, reversibility, and return value. No gaps remain.

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 meaningful context: explains the source of creative_id (sibling tools), default behavior for status, and account_id format/fallback. It goes beyond the schema but does not fully compensate for enums or format details already present.

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 creates a new ad inside an existing ad set, bound to a pre-existing creative, and returns the new ad ID. It distinguishes from sibling tools by explicitly referencing meta_ads_creatives_create and meta_ads_creatives_create_carousel as prerequisites.

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 guidance: it states when to use (after creating a creative via sibling tools), prerequisites (creative must exist, ad set must exist and not be DELETED), and default initial status (PAUSED). It implicitly tells when not to use by highlighting the need for a pre-existing creative.

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