meta_ads_creatives_create_lead

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

With no annotations provided, the description carries full behavioral disclosure. It discloses that the operation is 'Mutating — not automatically reversible' and recommends rollback recording, describes return values, and includes edge-case behavior such as 'image_url is rejected in video mode.' This is exemplary 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 concise and front-loaded, leading with the purpose and return values, then usage and prerequisites. Every sentence adds value, with no fluff or redundancy. It is well-structured for an AI agent to parse.

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 complex 12-parameter tool with no output schema or annotations, the description covers purpose, return values, mutation/rollback, usage conditions, prerequisites, and a key constraint (link_url). It provides sufficient context for an agent to select and invoke the tool correctly, and the schema covers the rest.

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?

The input schema provides 100% parameter coverage with detailed descriptions for all 12 parameters. The description text adds minimal new parameter-specific semantics; it repeats some schema info (e.g., link_url requirements) but does not meaningfully compensate beyond the schema's already high coverage. Baseline 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 states 'Creates a Lead Ad AdCreative attached to a Meta Instant Form' with a clear verb and specific resource, distinguishing it from sibling tools like meta_ads_creatives_create. It also states the return values, which further clarifies the tool's purpose.

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 explicitly says 'Use under a campaign with objective=OUTCOME_LEADS and an ad set with optimization_goal=LEAD_GENERATION' and provides prerequisites, e.g., 'the lead form must exist (create via meta_ads_lead_forms_create) and belong to the same Facebook Page.' This gives clear when-to-use and prerequisite guidance without needing explicit alternative comparisons.

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