Get Leads from Form

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

Annotations already mark readOnlyHint=true, and the description is consistent with that. The description adds useful context beyond annotations: the token-loading prerequisite and the return content ('field values, creation time, and ad info'). It does not discuss pagination mechanics in depth, but no contradiction or safety surprise exists.

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 compact and front-loaded, with a one-sentence purpose followed by structured Requires, Args, and Returns sections. There is no filler or redundant restating of the tool name.

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 retrieval tool with no output schema, the description covers the prerequisite, parameter meanings, and a return summary. It could be slightly more explicit about response_format and how the pagination cursor is used across calls, but the essential information is present.

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 adds meaning beyond the schema for key parameters: form_id is sourced from meta_list_leadgen_forms, page_id is used 'for authentication', limit has a range/default, and after is identified as a pagination cursor. It omits response_format, but the schema already documents that parameter with clear enum descriptions.

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 first sentence uses a specific verb ('Gets') and resource ('submitted leads from a lead generation form'), clearly distinguishing this tool from siblings like meta_list_leadgen_forms (which lists forms) and other page/content tools. The title also reinforces the action without ambiguity.

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 states a clear prerequisite: 'meta_list_pages must be called first to load page tokens,' and it points to meta_list_leadgen_forms as the source of form_id. It does not explicitly name alternatives or when-not-to-use conditions, but it provides enough operational context to guide an agent.

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