list_first_party_audiences

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention pagination, result limits, ordering, or whether the tool returns full details or summaries. The 'list' verb implies read-only, but no safety or performance traits are described.

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 (17 words) with front-loaded intent and parenthetical examples. Every word adds value, no redundant or irrelevant information.

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?

Given no output schema and no annotations, the description should at least hint at the return structure (e.g., audience IDs, names, sizes). It does not. For a tool with two optional parameters, the description covers basics but leaves significant gaps in what the agent needs to know.

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 states that parameters are filters for 'business unit or platform availability', but does not specify format or allowed values for business_unit, nor that platform is an enum. It adds general context but lacks precise semantics.

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 verb 'List' and the resource 'first-party audiences' with concrete examples (CRM lists, pixel-based, etc.). This distinguishes it from sibling tools like list_third_party_audience_layers, making it unambiguous.

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 is provided on when to use this tool versus alternatives such as get_audience_library_overview or list_third_party_audience_layers. The description only mentions filtering options but lacks explicit when-to-use or when-not-to-use instructions.

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