Get per-device results of a bulk policy cleanup job by providing the cleanup ID and device ID to verify status or outcome.
Get the per-device result of a bulk policy cleanup job.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Optional result format, e.g. text or json. | |
| device_id | Yes | ||
| cleanup_id | 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, so description carries full burden. It only states the basic function without disclosing any traits like whether the job must be completed, or what format the result takes. Minimal behavioral context.
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?
A single sentence that efficiently conveys the core purpose with no extraneous information. Properly front-loaded.
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 and no annotations, the description is too brief. It lacks context on how to interpret the per-device result, relationship to the cleanup job lifecycle, or expected behavior. Incomplete for a tool with 3 parameters and no additional metadata.
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 low (33%), only 'format' has a description. The tool description does not elaborate on 'cleanup_id' or 'device_id' beyond naming them. It adds no value over the schema, failing to compensate for the missing descriptions.
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 verb 'get' and the specific resource 'per-device result of a bulk policy cleanup job'. It distinguishes from sibling sdcloud_get_policy_cleanup_job which likely gets overall job status, by specifying 'per-device'.
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 explicit guidance on when to use this tool vs alternatives. The description implies it's for retrieving device-specific results after a cleanup job, but does not provide conditions or contrast with similar tools like sdcloud_get_policy_selective_deploy_job_device_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.