Create custom audience

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

Annotations mark readOnlyHint=false (mutation) and openWorldHint=true. The description adds valuable specifics: the audience starts empty, targetable remains false until large enough, and member loading is separate. No contradiction with annotations; it enriches them with concrete behavioral details.

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?

Three short sentences, each earning its place. The core purpose is front-loaded, followed by the workflow and a key behavioral constraint. No redundancy or fluff.

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 explains the initial state and subsequent steps but does not mention what the tool returns (e.g., the new audience ID). Since there is no output schema, the agent is left guessing about the response format. This is a notable gap for a creation tool.

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 only 33% (only account_id is described). The description adds a note that name must come from the user, which clarifies the name parameter. However, it does not explain the optional description parameter or add detail beyond the schema for account_id. Given low coverage, the description only partially compensates.

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 'Create an empty CRM custom audience,' which is a specific verb+resource statement. It clearly distinguishes this from update/delete siblings and even references the follow-up tool (x_ads_audience_users). The purpose is unambiguous.

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 implies a workflow: create the empty audience, then load members via x_ads_audience_users. It gives context for when this tool is appropriate (creation) but does not explicitly mention alternatives like update or delete for existing audiences. Still, the intended usage is clear.

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