meta_ads_leads_get

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

Discloses read-only nature and data retention policy ('Meta retains lead data for 90 days — pull regularly to avoid loss'). Lacks pagination details, but the schema's limit parameter provides some coverage. No annotation contradictions.

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?

Three short sentences, each serving a purpose: core function, recommended usage, and data retention warning. Front-loaded with the main action.

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?

Despite no output schema, the description enumerates returned fields (id, created_time, ad_id, campaign_id, form_id, field_data). Provides sibling differentiation and retention guidance. Covers essential context for an agent to use the tool 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%, so the description adds minimal value beyond parameter descriptions. The limit default and maximum are already documented in the schema. No new semantic insights provided.

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 starts with 'Retrieves submitted leads for a single form,' which is a clear verb+resource statement. It distinguishes from the sibling meta_ads_leads_get_by_ad by mentioning an alternative for leads attributed to specific ads.

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?

Explicitly states use cases: 'batch CRM sync or retrospective analysis.' Directs to an alternative tool for different scenarios: 'For leads attributed to a specific ad across forms use meta_ads_leads_get_by_ad.'

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