ghl_ad_fb_audience_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which clarify it's a safe read operation. The description adds the specific endpoint and required OAuth scopes (adPublishing.readonly), providing concrete behavioral context beyond the annotations.

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, containing two lines plus essential technical details (endpoint, OAuth). It is front-loaded with the main purpose and avoids unnecessary fluff, though it repeats the title verbatim.

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?

With no output schema provided, the description should at least hint at the return format (e.g., list of audience objects, fields returned). It does not, leaving a gap for agents to infer or default. For a simple list operation, this lack of return value clarity reduces completeness.

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% with descriptions, examples, and enums for all 4 parameters. The description does not add additional semantic details beyond what the schema already provides, so baseline score of 3 is appropriate.

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 title and description clearly state 'Get custom audiences' and 'Retrieve Facebook custom audiences for a location', indicating a list operation. The verb 'Get' combined with 'audience_list' in the name distinguishes it from related tools like ghl_ad_fb_audience_get (singular fetch), though not explicitly contrasted.

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 (e.g., ghl_ad_fb_audience_get for a single audience, ghl_ad_fb_audience_delete for deletion). There is no mention of prerequisites, limitations, or exclusions.

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