Remove a contact from an audience by specifying both the audience ID and the contact ID.
Remove a contact from an audience
| Name | Required | Description | Default |
|---|---|---|---|
| audience_id | Yes | Audience ID | |
| contact_id | Yes | Contact ID |
Changes observed during successful MCP inspections.
v1.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description carries full burden. It says 'Remove' but does not disclose whether deletion is permanent, reversible, or what side effects occur (e.g., impact on audiences or history).
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?
Description is a single sentence, but it omits crucial behavioral context that should be included. Under-specified rather than conciseness.
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?
For a deletion tool with no output schema and no annotations, the description should at minimum indicate permanence or side effects. It 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 coverage is 100% with basic descriptions ('Audience ID', 'Contact ID'), but the tool description adds no additional meaning beyond these. Baseline 3 for high coverage.
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 action ('Remove'), the resource ('a contact'), and the scope ('from an audience'). It distinguishes from sibling tools like create_contact, update_contact, and get_contact.
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?
No guidance on when to use this tool versus alternatives (e.g., archiving or deactivating a contact). No prerequisites or context for deletion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.