ga4_list_audiences

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

The description adds a key behavioral detail: it includes auto-created audiences such as 'All Users' and 'Purchasers' when a Google Ads link exists. It implies a read-only operation but does not disclose pagination, rate limits, or authentication needs. With no annotations provided, the description carries the burden and only partially covers behavioral aspects.

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, focused sentence that leads with the action and resource. It contains no filler and provides an important edge case (auto-created audiences) without redundancy.

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?

While the output schema exists and the tool is simple, the description fails to explain the property_id parameter, its optionality, or what happens when it is omitted. This gap in parameter semantics affects overall completeness, though the core purpose is clear.

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 sole parameter property_id is not explained in the description at all. Schema coverage is 0% and the description only vaguely mentions 'on a property' without connecting it to the parameter name or its optionality. The agent is left without any guidance on what value to provide.

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', the resource 'audiences', and the scope 'on a property'. It further distinguishes itself by noting it includes auto-created audiences from Google Ads links, which is specific and not mentioned by sibling tools like ga4_list_properties.

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 the tool is used to list audiences for a property, and there is a separate create tool (ga4_create_audience). However, it does not explicitly state when to use this tool versus alternatives or any exclusions, leaving room for ambiguity.

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