audiences_list_custom

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the basic function and does not mention pagination behavior, return format, ordering, authentication requirements, or any other operational details that would help an agent understand what to expect when invoking the tool.

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 a single sentence that is front-loaded and contains zero extraneous information. It is appropriately concise for the tool's simple function.

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?

Despite the low complexity, the description is incomplete given the absence of annotations and output schema. It does not explain the limit parameter, the shape of the returned list, or any behavioral nuances, leaving an agent without sufficient context to use the tool effectively beyond the basic call.

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 description coverage is 0%, so the description must compensate. It implicitly maps 'for an ad account' to the account_id parameter, but it does not explain the 'limit' parameter at all, leaving its meaning and effect (e.g., pagination or maximum number of items) undocumented.

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 identifies the resource 'custom audiences' with a scope 'for an ad account', clearly distinguishing it from sibling tools like audiences_list_saved or audiences_get_custom.

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 description implies usage when one needs to list custom audiences for a given ad account, but it does not explicitly state when to use this tool versus alternatives such as audiences_list_saved or audiences_get_custom. There are no exclusions or alternative recommendations.

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