meta_ads_leads_get

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

No annotations provided, so description carries full burden. It declares read-only, mentions 90-day data retention, and lists return fields. It could be improved by noting if pagination is supported (limit parameter hints at it) but overall covers key behavioral traits.

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?

Description is concise with three sentences: first states purpose and output, second gives usage context, third warns about data retention. Front-loaded with essential information, no wasted words.

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 no annotations, the description is remarkably complete. It lists return fields, explains usage scenarios, warns about data retention, and provides alternative tool. All necessary information for an AI agent to use correctly.

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 descriptions for each parameter. The description adds value by explaining account_id fallback to environment variable and default/max for limit. This enriches understanding beyond 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 clearly states the tool retrieves submitted leads for a single form, listing specific fields returned (id, created_time, ad_id, etc.). It distinguishes itself from siblings by specifying 'for a single form' and later mentioning an alternative for leads attributed to a specific ad across 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?

The description explicitly says 'Use this for batch CRM sync or retrospective analysis' and contrasts with meta_ads_leads_get_by_ad for leads across forms per ad. This provides clear guidance on when to use this tool and when not to.

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