audiences_create_saved

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

With no annotations provided, the description carries full burden. It discloses a known limitation (Meta returns code=3 unless Advanced Access is granted), which is a significant behavioral detail beyond the basic 'create' operation. It doesn't mention return values or other side effects, but the critical limitation is well-documented.

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 appropriately sized, front-loading the purpose in the first sentence and then clearly labeling the limitation. Every sentence contributes to understanding the tool, especially the critical error warning and workaround. It is concise without omitting essential caveats.

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 tool creates a saved audience with a complex targeting object, but the description is silent on parameter semantics, success returns, and other operational details. While the known limitation is helpful, it doesn't compensate for the lack of guidance on constructing inputs or interpreting outcomes. For a create tool with high complexity, this is incomplete.

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 0% and the description provides no information about any of the five parameters (account_id, name, targeting, confirm, description). The meaning of 'confirm' is particularly unclear, and the targeting object structure is undefined. The description adds no value beyond the raw schema titles.

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 opens with a clear, specific statement: 'Create a saved audience.' This identifies the exact verb and resource, and distinguishes it from sibling tools like audiences_update_saved or audiences_apply_to_adset by focusing on creation.

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 explicitly advises using audiences_apply_to_adset() as an alternative when a known error (code=3) occurs due to lack of Advanced Access, and warns that most MCP deployments lack this capability. This provides clear when-to-use and when-not-to-use guidance.

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