meta_ads_lead_forms_list

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

Declares the tool is 'Read-only' and explains the page ownership relationship. Without annotations, the description carries the transparency burden. It does not mention side effects or permissions beyond page admin access, but it sufficiently describes the tool's safe behavior.

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?

Three sentences with no redundancy. First sentence states core purpose, second lists output fields, third provides usage context and tool integration. Every sentence is essential and well-ordered.

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 compensates by listing return fields. It explains the tool's role in the broader workflow. Minor gap: does not explicitly mention pagination or that limit controls page size, but the schema's 'max 1000' implies it. Overall sufficient for an agent to invoke correctly.

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% with inline descriptions for all three parameters. The description adds value by explaining the account_id fallback logic and the contextual use of page_id. It ties the parameters to real-world workflow, e.g., 'page_id' is required because forms belong to Pages.

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 ('Lists'), resource ('lead forms configured for a Facebook Page'), and enumerates return fields (id, name, status, leads_count, locale, created_time). It distinguishes itself from siblings by noting its role in finding form_id for subsequent operations like meta_ads_leads_get.

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?

Provides explicit context on 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 that lead forms belong to Pages, not ad accounts. Does not explicitly state when not to use, but the guidance is sufficiently clear.

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