ga4_list_audiences

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

Annotations are absent, so the description carries the full burden. 'Lists' does signal a safe read-only operation, which is the core behavioral trait. However, it does not disclose that reslts are paginated (despite pageSize/pageToken params), what 'configured' includes or excludes, permissions needed, or response format. Adequate for the primary behavior but thin on everything beyond it.

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?

One sentence with the verb 'Lists' front-loaded and zero fluff. Every word contributes meaning: action, resourse, scope. The description is as efficient as a definition can be.

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?

For a simple tool — one required param, no nested objects, low polymorphic complexity — the sentence is sufficient to make a correct first call with propertyId. But with no output schema to document return values and two params left unexplained, the agent does not know the response shape, how pagination works, or what an audience entry contains. Minimum viable, no more.

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 only 33%, below the 50% threshold, so the description must compensate — and it does not. 'For a GA4 property' merely restates the schema's existing 'GA4 Property ID' for propertyId. pageSize (number bounded 1–200) and pageToken have no semantics in either the schema or the description, leaving two of three params unexplained.

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?

Verbs 'Lists' with a specific resourse 'configured audiences' scoped to 'a GA4 property' — unambigous and distinct. The resource name differentiates it from sibling ga4_list_* tools (accounts, properties, custom_dimensions, data_streams, conversion_events), though only implicitely; no explicit boundary statement. Clear enough for an agent to identify the right tool at a glance.

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 versus alternatives — no mention of sibling tools, no exclusions, no criteria like 'use ga4_list_data_streams for stream-level data instead'. The one-sentence description says nothing about when audiences are the right resourse or what consitutes a 'configured' audiience. An agent must infer usage purely from the tool name and sibling list.

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