meta_ads_audiences_list

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

No annotations provided, but the description declares 'Read-only' and notes that approximate counts may lag by 24–48h, adding important behavioral context. Could mention pagination, but the transparency is strong with the given information.

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 well-structured sentences: purpose and output fields, usage guidelines, and a data freshness caveat. Front-loaded with the most critical information, no superfluous content.

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 no output schema, the description lists all return fields and covers read-only nature and data lag. For a list tool, it is fairly complete; could add pagination details but overall sufficient.

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 with details on account_id format/fallback and limit default/max. The description adds no new parameter meaning beyond what the schema already provides, 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?

The description clearly states 'Lists Custom Audiences in a Meta Ads account' and enumerates the output fields (id, name, subtype, etc.), distinguishing it from sibling tools like audiences_create, audiences_get, and audiences_delete.

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 advises using this tool to find an audience_id before targeting an ad set (meta_ads_ad_sets_create/update) or creating a lookalike (audiences.create_lookalike), providing clear context and alternatives.

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