Remove multiple devices from Security Director Cloud in a single operation by specifying their UUIDs. Returns a job ID to track removal progress.
Bulk-remove devices. Body typically includes a list of device UUIDs to remove. Returns a job id; poll sdcloud_get_remove_devices_status for progress.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. |
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 must disclose behavioral traits. It mentions the operation returns a job ID and suggests polling, but it does not reveal whether the operation is destructive, idempotent, or what happens if devices are missing. This is insufficient for a removal action.
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 three sentences, front-loading the core action and then providing essential details about the body and expected result. No superfluous information.
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 the lack of output schema and the nested object parameter, the description covers the basics (what it does, what goes in body, how to track progress). However, it could be more complete by specifying the exact format of the body or potential error scenarios.
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?
The input schema has one parameter 'body' with a generic description. The tool description adds that the body typically includes a list of device UUIDs, which clarifies the parameter's content beyond the schema, adding meaningful context.
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 'Bulk-remove devices', specifying the verb (remove) and resource (devices). While it distinguishes from siblings like sdcloud_reboot_devices by focusing on removal, it does not explicitly differentiate from other device operations.
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 implies usage by stating body typically contains device UUIDs and that polling a status endpoint is needed. However, it gives no explicit guidance on when to use this tool versus alternatives or 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.