meta_ads_lead_forms_list

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

No annotations are provided, so the description carries the behavioral burden. It declares 'Read-only' and lists the exact return fields. It does not mention pagination or error handling, but for a simple list operation this is sufficient coverage.

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 compact and front-loaded. Each sentence adds value: purpose, return fields, read-only status, and usage guidance. No redundant or vague phrasing.

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?

Despite lacking an output schema, the description names the exact return fields. It provides clear usage context in the broader Meta Ads toolset, clarifies the page-vs-ad-account ownership, and mentions downstream tools. For a low-complexity list operation, this is complete.

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% with detailed descriptions for limit, page_id, and account_id. The description reinforces that page_id must reference a Page rather than an ad account, but adds minimal information beyond the schema. Baseline 3 applies because the schema handles parameter semantics.

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 uses the specific verb 'Lists' and identifies the resource as 'lead forms configured for a Facebook Page.' It distinguishes from sibling tools by noting that lead forms belong to Pages, not ad accounts, and enumerates the returned fields (id, name, status, leads_count, locale, created_time).

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: 'use this to find a form_id before attaching it to a Lead Ads creative or before pulling submitted lead data via meta_ads_leads_get.' Also clarifies ownership with 'Lead forms belong to Pages, not ad accounts,' which indicates the correct scope and helps avoid incorrect parameter usage.

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