Permanently delete a Braze dashboard user account through SCIM using the required user ID. Use it to deprovision user access when the account must be removed.
Delete a dashboard user account. This is permanent.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Braze REST API key (requires SCIM permissions) | |
| user_id | Yes | SCIM user ID to delete | |
| restEndpoint | No | Braze REST endpoint URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and does state the most important trait: the deletion is permanent. However, it omits required authorization details (though the schema's apiKey field mentions SCIM permissions), side effects on associated data, and error or recovery behavior.
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 extremely concise and front-loads the action and its most critical consequence. Both sentences earn their place without filler or redundancy.
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 destructive three-parameter tool with no annotations and no output schema, the description is minimally adequate because it warns that deletion is permanent. It does not cover when to use it, prerequisites, or side effects, so it leaves meaningful gaps for a destructive SCIM operation.
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%, so all three parameters are already documented in the input schema. The description adds no additional parameter meaning or format guidance beyond what the schema provides, making the baseline 3 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 gives a specific verb and resource: 'Delete a dashboard user account.' An agent can understand the core action, but it does not distinguish this from the sibling users_delete tool or clarify that this operates via SCIM rather than a standard user deletion path.
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?
There is no guidance on when to use scim_users_delete versus alternatives such as users_delete, nor any prerequisites or context for selecting this tool. The description only states the action and permanence, leaving usage entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.