Reboot multiple devices at once by submitting a list of device UUIDs. Get a job ID to monitor the reboot status.
Bulk-reboot devices. Body typically includes a list of device UUIDs. Returns a job id; poll sdcloud_get_reboot_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, the description carries full burden. It discloses the operation (bulk-reboot), async behavior, and follow-up polling. However, it omits potential side effects (e.g., service disruption) or permission requirements, which would be ideal for a mutating tool.
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 with three short sentences, each adding critical information. No redundant or irrelevant content, well front-loaded with the core action.
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 simple reboot tool with one parameter and no output schema, the description covers the essential aspects: action, parameter content, return value, and next step. It could be enhanced by specifying error conditions or exact parameter format, but it is largely complete.
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 schema's body description is generic ('JSON request body matching the target Security Director Cloud schema'), but the description adds meaningful guidance: 'typically includes a list of device UUIDs.' This clarifies the expected content 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 'Bulk-reboot devices' with a specific verb (reboot) and resource (devices). It distinguishes from sibling tools like sdcloud_remove_devices by focusing on reboot functionality.
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 guidance on the body parameter ('list of device UUIDs') and indicates the asynchronous nature (returns job id to poll). While it doesn't explicitly list alternatives or when-not-to-use, the context is clear enough for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.