meta_ads_lead_forms_create

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

With no annotations, the description carries the burden of disclosure. It clearly states the tool is mutating, reversible, and that rollback archives rather than deletes leads. It could be more explicit about side effects, but it provides sufficient behavioral 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?

The description is a single paragraph of about 120 words, with the core purpose stated upfront. Every sentence provides necessary information without redundancy or fluff.

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 and a complex tool with nested objects, the description covers mutation, reversibility, and key requirements. The return value is stated. It could mention error scenarios, but overall it is complete enough for an agent.

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%, but the description adds significant value by explaining the question structure (ordered list, standard vs CUSTOM types), account_id fallback behavior, and the privacy policy requirement. This goes beyond the schema alone.

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 action ('Creates a new lead form on a Facebook Page') and the result ('Returns the new form_id'). It distinguishes itself from sibling tools like meta_ads_lead_forms_get and meta_ads_lead_forms_list by being the creation endpoint.

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?

While it mentions the tool is mutating and reversible via rollback_apply, it does not explicitly state when to use this tool versus alternatives (e.g., manual creation in Ads Manager) or provide exclusions. The privacy policy requirement is noted, but no direct comparison to other tools.

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