meta_ads_audiences_list

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

No annotations provided, so description must cover behavioral traits. It declares 'Read-only', explains the optional account_id with fallback, and warns that approximate counts may lag by 24-48 hours. Fully transparent.

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?

Four sentences efficiently cover purpose, output, usage, and a data freshness caveat. No extraneous information; every sentence earns its place.

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?

Since no output schema exists, description adequately describes return fields and behavior. Given the tool's simplicity and the richness of the description, it is contextually complete.

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%, but description adds value: clarifies account_id format with 'act_' prefix and fallback, and notes limit max per Meta API. Enhances schema information.

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?

Clearly states 'Lists Custom Audiences in a Meta Ads account' and enumerates return fields (id, name, subtype, etc.). Distinguishes from sibling tools like meta_ads_audiences_create_lookalike and meta_ads_ad_sets_create by specifying its role in finding an audience_id.

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 says 'Use this to find an audience_id before targeting an ad set or before creating a lookalike', linking to relevant sibling tools. While it doesn't provide negative usage cases, the context is clear and actionable.

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