list_custom_audiences

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

Discloses that the tool flags unusable, too small, too broad, stale, or errored audiences, which adds behavioral context. However, no explicit mention of read-only nature or potential side effects. With no annotations, the description carries the burden but is adequate.

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?

Short, front-loaded description with no fluff. Every sentence adds value, clearly structured with purpose followed by parameter details.

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?

Fairly complete for a list tool: explains what is returned and flags issues. Parameter documentation covers both args. Lacks details on pagination or return structure, but overall sufficient given no output schema.

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?

Adds meaning beyond schema by providing an example format for account_id and explaining the default for limit. With 0% schema description coverage, this is helpful but still limited; does not describe constraints or allowed values.

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 the action (list), resource (custom audiences), and specific information returned (type classification, size estimates, delivery status, diagnostic warnings). Distinguishes from sibling tools like estimate_audience_size and get_account_info.

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?

No guidance on when to use this tool vs alternatives. Does not mention scenarios where this is preferred or alternatives like other list tools.

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