meta_ads_lead_forms_create

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

No annotations are provided, so the description carries the burden. It discloses that the tool is 'Mutating, reversible via rollback_apply' and explains the rollback behavior (archives form, does not delete leads). It also mentions Meta's policy requirement for privacy_policy_url. This is good behavioral 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 sentences long, front-loaded with purpose, and includes critical behavioral notes (mutability, reversibility, policy requirement). Every sentence contributes value with 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?

Given no output schema, the description explains the return value (form_id). It covers mutation, reversibility, and policy constraints. For a create tool, it provides sufficient context for an agent to understand the action and side effects.

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 context about question ordering and standard types, but the schema already describes each parameter thoroughly. The description does not add significant new meaning beyond summarizing key 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 'Creates a new lead form on a Facebook Page' and notes the return of form_id. This is a specific verb+resource pairing that distinguishes it from sibling tools like meta_ads_lead_forms_get and meta_ads_lead_forms_list.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks context about prerequisites, when not to use, or comparisons to other lead form tools (e.g., when to create vs. get vs. list).

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