Soft-delete multiple contacts in one call by passing their UUIDs. Use it to remove many contacts at once instead of deleting them individually.
Soft-delete many contacts in a single call. Requires contacts:delete.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Contact UUIDs to delete |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that deletion is "soft" and requires contacts:delete, but it omits batch-size limits, partial-failure behavior, recoverability details, and what the operation returns.
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?
Two short sentences, front-loaded with the core action and followed by the permission requirement. There is no wasted prose.
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 one-parameter bulk mutation with no output schema and no annotations, the description is minimally adequate: it names the operation, soft-delete semantics, and required permission. It nonetheless leaves out important operational context such as batch limits, failure handling, and differentiation from the matching-based bulk delete sibling.
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 100%, and the single parameter is already documented as "Contact UUIDs to delete." The description adds no syntax, formatting, or batching detail beyond the schema baseline.
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 specific verb and resource: "Soft-delete many contacts in a single call." It clearly indicates bulk deletion, but does not distinguish this ids-based operation from the sibling conduyt_bulk_delete_contacts_matching or the single conduyt_delete_contact tool.
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 only usage-related information is the permission prerequisite "Requires contacts:delete." There is no explicit guidance on when to use this tool versus deleting one contact or using the matching/filter-based bulk delete sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.