meta_ads_leads_get

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

No annotations are provided, so the description bears full responsibility. It declares 'Read-only' and warns about data retention: 'Meta retains lead data for 90 days — pull regularly to avoid loss.' It also lists return fields. However, it does not mention authentication, rate limits, or error handling, which could be more transparent.

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 three sentences, each serving a purpose: functional summary, use case, and alternative/warning. No superfluous words; it is efficient and front-loaded.

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 the tool has 3 parameters, no output schema, and no annotations, the description covers key aspects: purpose, return fields, read-only nature, use case, alternative, and data retention policy. It lacks details on pagination or error states, but is largely complete for a fetch operation.

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 100%, and the description adds value beyond the schema by noting that account_id is optional and falls back to configured credentials, and that limit defaults to 100 with max 1000. This provides practical usage context.

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 'Retrieves submitted leads for a single form.' It specifies the verb (retrieves) and resource (leads for a form). It differentiates from sibling tool meta_ads_leads_get_by_ad by noting 'For leads attributed to a specific ad across forms use meta_ads_leads_get_by_ad.'

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 states when to use: 'for batch CRM sync or retrospective analysis.' It also provides an alternative: 'For leads attributed to a specific ad across forms use meta_ads_leads_get_by_ad.' This clearly distinguishes when not to use this tool.

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