sdcloud_get_policy_selective_deploy_job

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

No annotations are provided, so the description carries full responsibility. It only says 'Get the status' but does not disclose what the response contains, whether it is idempotent, error conditions, performance implications, or any side effects. The description is insufficient for an agent to understand tool behavior beyond the basic 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 a single sentence with no fluff, but it is excessively brief for a tool with no annotations or output schema. It meets the minimum threshold for conciseness but sacrifices informative content. Structure is flat with no front-loading of critical details.

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 annotations, output schema, and parameter descriptions, the tool description is incomplete. It tells the core action but omits return value details, possible errors, and usage context. For a simple status-check tool, this might be borderline sufficient, but given the context signals (0% schema coverage, no output schema), more information is needed.

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 required parameter 'selective_deploy_id' with 0% description coverage (no schema description). The tool description does not add any additional meaning, format, or usage hints for this parameter. The parameter name is self-explanatory but the description fails to clarify its origin, constraints, or format (e.g., UUID).

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 tool retrieves status of a bulk policy selective-deploy job by ID. The verb 'get' and resource 'status of a bulk policy selective-deploy job' are specific. The name distinguishes it from sibling tools like 'sdcloud_start_policy_selective_deploy_job' (starts) and 'sdcloud_get_policy_selective_deploy_job_device_status' (per-device status).

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 such as 'sdcloud_get_policy_deploy_job' or 'sdcloud_get_policy_selective_deploy_job_device_status'. The description does not mention prerequisites (e.g., needing a prior start call) or conditions that make it appropriate.

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