meta_ads_leads_get

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

No annotations are provided, so the description carries the full burden. It explicitly states 'Read-only' and discloses the 90-day data retention policy, adding valuable behavioral context beyond the schema. It lacks details on pagination or rate limits, but for a simple read tool, this is sufficient.

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 well-structured: main action, return fields, usage guidance, alternative, and a retention warning. Every sentence contributes value, and it is front-loaded with the core purpose.

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?

Without an output schema, the description lists the key return fields and explains the field_data structure. It covers purpose, usage, alternatives, and a caveat. Minor gaps remain around pagination behavior, but the limit parameter is documented, making it complete enough for correct invocation.

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 input schema has 100% description coverage for all three parameters, so the description does not need to explain them. The tool description adds no parameter-specific semantics, and the baseline of 3 is appropriate since the schema already handles it.

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, with a specific verb and resource. It lists the return fields and explicitly distinguishes it from the sibling tool meta_ads_leads_get_by_ad, making its scope unambiguous.

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?

Provides explicit guidance: 'Use this for batch CRM sync or retrospective analysis' and names an alternative tool for ad-filtered leads. The 90-day retention warning also informs when to use it regularly.

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