delete_audience_members

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

No annotations provided, so description carries full burden. It discloses the primary behavior (removing members) and warns that removing all members may delete the audience. While it doesn't explicitly label the operation as destructive, the warning suffices.

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 concise sentences, no fluff. First sentence states purpose, second gives usage hint, third warns of side effect. Front-loaded and efficient.

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 low complexity (2 params, no output schema), description covers purpose, parameter usage, and a key side effect. It could mention return value (e.g., success or count), but not strictly necessary.

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 covers both parameters. Description adds value by explaining how to obtain member IDs (via get_audience_members or search_audience_members), which is not in the schema. For audience_id, no extra info is added beyond schema.

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?

Description clearly states the verb (remove), resource (specific members from an audience), and method (by member IDs). It distinguishes from sibling tools like add_audience_members and get_audience_members.

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?

Provides guidance to first find member IDs using get_audience_members or search_audience_members, and warns about potential audience deletion if all members are removed. However, it does not explicitly state when not to use or alternative tools for removing entire audience.

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