meta_ads_lead_forms_create

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

With no annotations, the description fully covers behavioral traits: it states it's mutating, not automatically reversible, suggests recording before-state for rollback, and explains key behaviors like the 3-step form for is_higher_intent and the superseding of follow_up_action_url by thank_you_page. Minor omission: no mention of rate limits or auth requirements.

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 at 4 sentences, front-loads purpose and return value, and covers essential details without fluff. However, it could be more structured with bullet points for parameter groups, but it remains readable and to the point.

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 11 parameters (4 required), nested objects, and no output schema, the description covers the return value, rollback guidance, and parameter behaviors. It addresses the most important aspects, though it omits potential error scenarios or response format details.

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 significant value: it lists standard Meta types, details CUSTOM requirements, explains privacy_policy_url is mandatory by policy, notes context_card lifts conversion rate, describes is_higher_intent's effect on lead quality, and explains conditional_questions_choices branching logic. This goes well beyond the schema.

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 lead form on a Facebook Page and returns the form_id. This specific verb+resource combination distinguishes it from sibling tools like get, list, update, and duplicate.

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 explicitly differentiate when to use this tool versus alternatives like meta_ads_lead_forms_duplicate or update. It provides guidance on the mutating nature and rollback suggestion, but lacks explicit when-to-use or when-not-to-use context relative to siblings.

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