List Custom Audiences

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

With no annotations, the description must carry the burden of behavioral disclosure. It clarifies that the operation lists audiences for the current ad account and that intended_use filters eligible audiences, but it omits important behaviors such as pagination, default limits, whether archived or deleted audiences appear, and response shape.

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?

The description is two sentences with no filler, front-loading the core action and scope before adding a compact parameter tip. Every phrase contributes meaning, making this an appropriately sized, well-structured definition.

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?

For a simple list tool with three optional parameters, the description gives a workable baseline, but it is not fully complete. There is no output schema, so return format is not clarified, and behavioral details like limits and pagination are absent, meaning an agent may still guess at some invocation details.

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 schema already documents intended_use and custom_audience_ids, and the description adds a useful clarification that intended_use filters only eligible audiences. However, the 'limit' parameter is undocumented in both schema and description, and the description does not explain how custom_audience_ids interacts with the list operation.

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 uses a specific verb ('List') and a clear resource ('custom audiences for the current ad account'), so an agent can tell this is a read/list operation scoped to the active account. It does not explicitly contrast itself with sibling tools like get_custom_audience, so it stops just short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus siblings such as get_custom_audience, create_custom_audience, or merge_custom_audiences. The only usage note is about filtering by intended_use, which is parameter-level advice rather than tool-selection guidance.

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