meta_ads_leads_get_by_ad

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

With no annotations provided, the description carries the transparency burden. It explicitly states 'Read-only' and clarifies the return shape ('same lead record shape as meta_ads_leads_get'). It does not discuss pagination or rate limits, but the schema already describes limit behavior.

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 tight sentences: first states the action and scope, second asserts read-only safety, third gives use case and alternative. Every sentence adds value and the key verb is 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?

No output schema exists, but the description compensates by referencing meta_ads_leads_get for the record shape. The param schema is complete, and the use case is explicit. It could mention pagination explicitly, but this is a minor gap for a straightforward read-only fetcher.

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 detailed descriptions for ad_id, limit, and account_id. The description adds only contextual reinforcement ('specific ad', 'ad ID') and does not provide additional parameter semantics beyond the schema, so baseline 3 is appropriate.

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?

Clear verb 'Retrieves leads' with a specific resource ('a specific ad') and scoping ('regardless of which form they used'). Explicitly distinguishes itself from meta_ads_leads_get by contrasting per-ad vs cross-ad lead pulls.

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 when-to-use guidance: 'measure lead volume of a particular creative / ad ID when ranking winners.' Also names the alternative meta_ads_leads_get for 'full form-based lead pulls (cross-ad)', giving clear exclusion criteria.

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