meta_ads_lead_forms_list

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

With no annotations, the description carries full burden. It correctly labels the tool as 'Read-only' and mentions the return fields. However, it does not disclose details like whether pagination continues beyond the limit, auth scope beyond admin page access, or any rate-limiting considerations. Adequate but lacks depth.

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 efficient, front-loading the purpose in the first sentence and then adding operational context. It contains no superfluous words, though it could be slightly tighter by combining the last two sentences.

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 three parameters, the description covers the tool's role, parameter specifics, and usage sequence. It mentions return fields and read-only behavior. Missing detail on pagination continuation or response structure, but overall complete for a list tool.

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?

Input schema coverage is 100%, so baseline is 3. The description adds context for account_id (optional, falls back to env var) and page_id (must have admin access), which slightly enriches the schema definitions but does not provide critical new information.

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 return fields (id, name, status, leads_count, locale, created_time). It distinguishes from siblings by noting it is for Pages, not ad accounts, and positions it as a prerequisite for attaching to Lead Ads creative or fetching leads via 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?

The description explicitly explains that lead forms belong to Pages, not ad accounts, and advises using this tool to find a form_id before attaching it to a Lead Ads creative or pulling lead data. This provides clear context and alternative tools, though it does not explicitly list exclusions.

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