sdcloud_get_policy_selective_deploy_job_device_status

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full behavioral disclosure burden. It indicates a read operation ('Get') but does not mention idempotency, required job state, potential error cases, or output format limitations. Very limited behavioral insight.

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 clear sentence with no unnecessary words. It is front-loaded with the essential action and scope. Could slightly benefit from adding a note about required job state but remains concise and efficient.

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?

The tool has no output schema, and the description does not indicate what fields the per-device result contains (e.g., status, error messages). Given the complexity of the sibling set and the missing output schema, the description is incomplete for an agent to understand the full context.

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?

Only the 'format' parameter has a description in the schema ('Optional result format, e.g. text or json'), covering 33% of parameters. The description adds no extra meaning to device_id or selective_deploy_id, failing to compensate for the low schema coverage.

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 it retrieves per-device results for a selective deploy job. It distinctively differentiates from sibling tools like sdcloud_get_policy_selective_deploy_job (which likely gets the job summary) and other per-device status tools for different job types (deploy, preview, cleanup).

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 vs alternatives, such as prerequisites like job completion status or when to prefer this over the summary job tool. It only states what it does without contextual usage tips.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.