Create Saved Audience

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

Annotations indicate readOnlyHint=false and destructiveHint=false, implying mutation. The description confirms creation, which is consistent. However, it does not disclose side effects (e.g., overwriting existing audience names) or any rate limits. The description adds minimal 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 efficient: one sentence for purpose followed by a parameter list. It is front-loaded and contains no filler. However, the parameter list could be omitted since the schema covers the same information, but it's not harmful.

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 details about return values, error handling, or what constitutes a successful creation. The targeting object is complex but not explained. Given no output schema, this is a gap. The description is minimal and relies on the user knowing the API.

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 50%, with only response_format and targeting having descriptions. The description repeats parameter names and types without adding meaning: 'ad_account_id (string): Ad account ID' is tautological. It provides no guidance on how to construct the targeting object, which is a complex parameter.

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 it creates a saved audience (reusable targeting preset) for an ad account. The verb 'creates' and resource 'saved audience' are specific, and it distinguishes from sibling tools like meta_create_custom_audience or meta_create_lookalike_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 versus alternatives like meta_create_custom_audience or meta_create_lookalike_audience. No mention of prerequisites, such as requiring an ad account ID or the need for admin permissions.

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