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 full burden. It declares the tool as 'Read-only' and mentions that account_id is optional (falls back to credentials). However, it lacks disclosure of potential errors, rate limits, or auth requirements beyond implicit understanding.

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 two sentences with no filler. The first sentence states function and output fields; the second provides usage context. Every sentence adds value.

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?

For a list tool without output schema, it explains returned fields and usage within the Meta Ads workflow. It mentions the relationship to sibling tools and the page ownership constraint. Could mention pagination, but limit parameter covers that.

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 detailed parameter descriptions in the schema. The tool description adds context about page_id's ownership but does not significantly go beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 'Lists lead forms configured for a Facebook Page' and specifies returned fields (id, name, status, leads_count, locale, created_time). It distinguishes itself from siblings like meta_ads_leads_get (which pulls lead data) and meta_ads_lead_forms_create (creation).

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 explicitly says to use this tool before attaching a form to a Lead Ads creative or before pulling submitted lead data. It notes that lead forms belong to Pages, not ad accounts, guiding correct usage. While it doesn't explicitly state when not to use it, the context is clear.

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