Delete an IPS profile using its UUID to remove unwanted intrusion prevention configurations from Security Director Cloud.
Delete an IPS profile object by UUID.
| 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?
With no annotations provided, the description carries full burden but only states 'delete' without clarifying permanence, authorization needs, or side effects. This is insufficient for a destructive operation.
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 a single, short sentence that is efficient and front-loaded. However, it might be too sparse given the lack of other informative elements.
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 no output schema, annotations, or parameter details, the description is incomplete for a deletion tool. It does not describe return value, success/failure indicators, or prerequisites.
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 0%, so the description must compensate. It adds 'by UUID' to clarify the parameter's role, but does not explain format, how to obtain it, or that it is required. Minimal addition beyond the 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?
The description clearly states the action 'delete' and the resource 'IPS profile object', and identifies the identifier 'by UUID'. It distinguishes this tool from siblings like 'sdcloud_create_ips_profile' or 'sdcloud_list_ips_profiles'.
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 description provides no guidance on when to use this tool versus alternatives, such as prerequisites (e.g., existence of the profile), or the irreversibility of the action. It does not mention when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.