Delete a user account from HPE Security Director Cloud by its unique UUID to remove access and clean up tenant administration.
Delete a user by uuid. Note: unlike get/update, the API spec names this path param "uuid" rather than "user_id".
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only notes a parameter naming inconsistency but does not disclose consequences (e.g., irreversibility, cascading effects). The destructive nature is implicit.
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 concise sentences with minimal fluff. Purpose is front-loaded, and the additional note is relevant.
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 delete operation with no annotations and no output schema, the description lacks critical context such as prerequisites, permissions, or side effects. Incomplete for safe agent usage.
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 has 0% description coverage. The description adds value by clarifying that the 'uuid' parameter is the same identifier used as 'user_id' in get/update, helping agents map the parameter correctly.
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 clearly states 'Delete a user by uuid', specifying the action and resource. It distinguishes from sibling tools like get/update by noting the parameter name difference, but does not explicitly differentiate from other delete tools.
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., when not to delete a user). The note about the parameter name is a technical detail, not usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.