Remove a specific certificate from a device using its UUID and certificate ID/type. Helps clean up expired or unused certificates.
Delete a certificate from a device. Body typically includes the certificate id/type to remove.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| device_uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description must disclose behavioral traits. It indicates a destructive operation ('Delete') but lacks details on consequences, authentication needs, or error handling.
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 no redundancy or superfluous information. 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?
Given the complexity (nested body object, no output schema, no annotations), the description is too minimal. It fails to specify the body structure, return values, or success criteria, leaving the agent under-informed.
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 50% (body has description, device_uuid has none). The description adds context for the body parameter ('typically includes the certificate id/type'), partially compensating. Device_uuid remains unexplained.
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 a certificate from a device') and resource, distinguishing it from sibling tools that handle other certificate operations (e.g., install, list). The mention of 'certificate id/type' adds specificity.
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 like sdcloud_list_device_certificates or sdcloud_install_device_ca_certificate. No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.