meta_ads_ads_create

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

Discloses mutating behavior (via 'Creates' and 'mutating'), reversibility, and default initial status. Without annotations, this is strong but could mention potential side effects or rate limits. Adds value beyond the schema by explaining the lifecycle context.

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?

Four sentences, front-loaded with the core action. Each sentence adds value (action, return, mutability/reversibility, status, prerequisite with sibling tools). No wasted words.

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 5-param create tool with no output schema, the description covers return value (new ad id), prerequisite (creative must exist), default status, and reversibility. It also provides sibling tool references for creative creation. No gaps for typical usage.

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 coverage is 100%, but the description adds context: it clarifies that creative_id must refer to an existing creative (prerequisite), and status defaults to PAUSED. This goes beyond the schema descriptions, which only state format and requirements.

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 it creates an ad inside an existing ad set, binding it to a pre-existing creative. It specifies the verb (creates) and resource (ad), and distinguishes from sibling creative-creation tools by mentioning them 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?

Explicitly states when to use (after creative exists), warns of prerequisite (creative must be pre-created via sibling tools), and mentions reversibility via rollback_apply. Also notes default status (PAUSED) and that ACTIVE requires operator sign-off.

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