list_audiences

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List' and gives no details about pagination, limits, ordering, required permissions, or any side effects. This is minimal for a read operation and leaves important behavioral aspects undisclosed.

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, concise sentence that directly states the tool's purpose. There is no filler, and the key information is front-loaded, making it easy to scan.

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 the simplicity of the tool (one parameter) and the existence of an output schema, the description is adequate but not complete. It lacks behavioral context like pagination or error handling, and the parameter is not explained. It covers the basic purpose but leaves gaps that could be filled with more detail.

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 coverage is 0%, so the description must compensate for explaining parameters. The only parameter, property_id, is not described beyond its name. The description offers no additional meaning, such as format, required scope, or how it relates to the GA4 property.

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 tool's function: listing audiences on a GA4 property. It uses a specific verb ('List') and resource ('audiences'), and the scope ('on a GA4 property') distinguishes it from sibling tools like list_account_summaries or list_data_streams.

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 when you need to see audiences for a given property, but it does not explicitly state when to use it vs alternatives. Since sibling tools target different resources, the usage context is somewhat clear but no exclusions or alternative references are provided.

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