ad_manager_fb_remove_custom_audience_member

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered. The description adds no behavioral context beyond that—it doesn't explain consequences (e.g., permanent removal) or any side effects. It fails to enrich the agent's understanding of the operation.

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 (one sentence) but is essentially a restatement of the tool name, providing no additional structure or front-loaded value. It's not verbose, but it's not optimally structured to convey useful information beyond the obvious.

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 that this is a destructive operation, the description should explain when it's appropriate (e.g., removing a contact from a custom audience) and any implications. It doesn't mention required identifiers beyond what the schema lists, nor any validation or error conditions. For a destructive tool, the description 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?

All four parameters are described in the schema with adequate detail, so schema coverage is 100%. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline 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 description states a clear verb+resource: 'Remove custom audience member'. This distinguishes it from sibling tools like add_custom_audience_member and batch_update_audience_members. However, it lacks context about scope (e.g., which audience types) and is essentially a restatement of the tool name, so it's clear but not enhanced.

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. There is no mention of prerequisites (e.g., needing an existing audience member) or when a different tool like batch_update might be preferable. It simply states the action.

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