List Lead Gen Forms

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

Annotations already mark the operation read-only and non-destructive; the description adds a meaningful dependency on page tokens from meta_list_pages and lists the returned fields. This is useful behavioral context beyond the annotations, though pagination behavior is not disclosed.

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 well-structured and reasonably concise: purpose, context, prerequisite, args, and return values are each separated. It earns its length, though the Args section restates schema information.

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?

The description provides the critical prerequisite and return fields, but it leaves the 'after' pagination parameter undocumented and does not mention pagination behavior. Given no output schema, the missing parameter context makes this only minimally 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?

The description repeats page_id and limit semantics already present in the schema and does not explain the 'after' parameter, which has no schema description. It also omits response_format, so the parameters are only partially covered and the description adds little beyond the schema.

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 opens with a specific action and resource: 'Lists lead generation forms for a Facebook Page.' It is clear about what the tool does, but it does not explicitly name or contrast with sibling tools such as meta_get_leadgen_leads, so differentiation is left to the reader.

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?

It gives explicit context: lead forms are tied to OUTCOME_LEADS campaigns, and it states a required prerequisite ('meta_list_pages must be called first to load page tokens'). It does not discuss when not to use the tool or mention alternative tools.

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