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

The annotations already establish that this is a read-only, open-world, non-destructive operation, so the safety profile is covered. The description adds useful context by naming the fields returned, but it does not explain permissions, pagination, or the distinction between listing forms and retrieving submitted leads.

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 a single efficient sentence with no filler. It is appropriately short, though it could be front-loaded more explicitly with a verb such as 'List' to clarify the operation immediately.

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 read-only listing tool with annotations and a mostly documented schema, the description is adequate but thin. Because there is no output schema, it should do more to explain the return shape, pagination, or how this differs from meta_get_leads.

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 80%, so most parameters are already explained by the schema, including detail, folder, account, and language. The description adds no parameter-specific meaning beyond the schema, and the required page_id parameter remains undocumented in both the schema and the description.

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 identifies the resource as instant lead forms on a Facebook Page and lists the returned attributes: status, lead count, and creation date. It stops short of explicitly distinguishing the tool from related siblings such as meta_get_leads, which likely retrieves the actual lead submissions rather than the forms.

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?

There is no guidance on when to use this tool versus alternatives such as meta_get_leads or the lead-form tools for LinkedIn and TikTok. It also does not state prerequisites, exclusions, or the workflow context for listing forms before retrieving leads.

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