meta_ads_leads_get_by_ad

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

Declares 'Read-only' for safety, despite no annotations. References same record shape as sibling tool. Lacks detail on pagination or errors but sufficient for a read operation.

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 concise sentences: core function, read-only and shape reference, usage guidance. No fluff, front-loaded with the most critical info.

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 but description references sibling tool's shape, reducing need for full detail. Usage guidance and param coverage are adequate for the task.

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 already. Description adds 'regardless of form used' which clarifies scope but does not significantly enhance param understanding.

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' with specific resource 'leads attributed to a specific ad'. Distinguishes from sibling meta_ads_leads_get by noting same shape and cross-ad use case.

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 when to use (measure lead volume per ad) and when not (use meta_ads_leads_get for cross-ad). Directly addresses ranking winners.

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