ghl_ad_google_audience_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which inform safety. The description adds the endpoint method (GET) and required OAuth scope, but does not disclose additional behavioral traits like pagination, rate limits, or response structure. Since annotations cover the safety profile, a score of 3 is appropriate.

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 concise with three sentences covering purpose, endpoint, and scopes. The first sentence ('Get audiences') is slightly redundant but not harmful. No wasted words.

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?

The description lacks mention of the return format (list of audiences), the filtering role of the 'isDraft' parameter, and any pagination or response limits. Given no output schema, these omissions leave the agent underinformed about what to expect and how to use the parameters effectively.

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?

Input schema coverage is 100%, and both parameters (locationId, isDraft) have descriptions and examples in the schema. The description does not add any semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 retrieves 'Google Ads combined audiences for a location,' specifying the verb 'Retrieve' and the resource. The endpoint and OAuth scope provide additional context. However, it does not explicitly differentiate from the sibling 'ghl_ad_google_audience_get' tool.

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 like 'ghl_ad_google_audience_get' or Facebook audience tools. The description only states the OAuth scope, missing explicit when-to-use or when-not-to-use advice.

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