List Saved Audiences

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe, read-only behavior. The description adds no context beyond the name 'Lists', such as pagination behavior, rate limit implications, or what happens when there are no saved audiences.

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 very concise (3 lines) and front-loaded with the purpose. However, it is too brief, missing opportunities to add key details without increasing length significantly.

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 tool has 4 parameters, no output schema, and limited annotations, the description is incomplete. It does not explain pagination parameters (limit, after), output format choices, or typical usage patterns. A more complete description would include these aspects.

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 input schema has 4 parameters, but only 25% have descriptions (response_format). The description documents only ad_account_id, repeating the schema's property name without adding meaning. It omits details for limit, after, and response_format, failing to clarify pagination or format options.

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 'Lists saved audiences (targeting presets) for an ad account.' It uses a specific verb ('Lists') and resource ('saved audiences'), and distinguishes from siblings like meta_create_saved_audience and meta_delete_saved_audience.

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 provides no guidance on when to use this tool vs alternatives, such as meta_get_custom_audience or meta_search_targeting_interests. There is no mention of prerequisites, when-not-to-use, or exclusions.

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