meta_ads_conversions_send_lead

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

States mutating nature and deduplication behavior via event_id, but does not disclose rate limits, permission requirements, or detailed side effects. With no annotations, more behavioral context would be beneficial.

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?

Concise and well-structured: purpose, acknowledgment, mutation note, usage guidance, examples, all in a few sentences. No redundant information.

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?

Covers purpose, usage, and parameters thoroughly, but lacks description of the return format beyond 'events_received acknowledgement'. With no output schema, stating the response structure would improve completeness.

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?

All 6 parameters have schema descriptions, and the description adds valuable context: account_id fallback, pixel_id dedupe, event_time 7-day constraint, user_data hashing and supported keys, event_source_url requirement, test_event_code usage.

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 sends a single Lead event via Meta Conversions API, distinguishing it from siblings 'meta_ads_conversions_send_purchase' (money-moving events) and 'meta_ads_conversions_send' (non-standard event names).

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 for form submissions, trial signups, demo requests (non-monetary), and explicitly excludes money-moving events (use purchase) and non-standard events (use send).

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