list_custom_audiences

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

No annotations are provided, so the description carries the burden. The verb 'Liste' implies a read-only retrieval operation, and the ad_account_id format is a useful operational detail. However, it does not disclose pagination, ordering, limit behavior, or error scenarios, though an output schema is present.

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 short sentences with no filler. The first sentence clearly states what the tool does, and the second provides the essential ID format. 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?

Although simple, the definition is mostly complete: it identifies the target ad account, provides the required format, and the output schema covers return structure. It lacks explicit alternative tool guidance and pagination/limit semantics, but these are minor for a straightforward list endpoint.

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 description adds meaningful format guidance for ad_account_id ('act_123456789'), which is not present in the schema. It does not explain the limit parameter, but the name and default of 50 make its basic purpose understandable. With 0% schema coverage, this is partial but not full compensation.

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 action ('Liste') and the resource ('audiences personnalisées') scoped to an advertising account. This distinguishes it from singular/related tools like get_custom_audience, create_custom_audience, and delete_custom_audience.

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?

The intended use is implied: list custom audiences for a given ad account. However, there is no explicit guidance on when to prefer this over get_custom_audience or how it differs from sibling tools, so the agent must infer the routing from names alone.

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