sdcloud_start_policy_selective_deploy_job

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

With no annotations provided, the description must disclose behavioral traits. It explains the operation (starting a job to deploy multiple policies to a subset of devices) but does not mention job type (async/sync), return value, or how the subset is specified. Missing details typical for job-starting tools.

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: first states purpose, second provides sibling differentiation. No fluff, front-loaded with key information.

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 job-starting tool with no output schema and a generic body parameter, the description is missing details on job lifecycle, how to check status (despite sibling get_job tools), and body structure. Adequate but not fully complete for an agent to use without prior 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?

Schema coverage is 100% with one body parameter described as 'JSON request body matching the target Security Director Cloud schema.' The description adds no further meaning beyond the schema, meeting the baseline of 3 for high 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 the tool starts a bulk selective-deploy job and distinguishes it from single-policy tools by noting it operates across all policies in the request body. The verb 'start' and resource 'bulk selective-deploy job' are specific and unambiguous.

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 explicitly differentiates this tool from single-policy tools like sdcloud_{deploy,preview,cleanup,selective_deploy}_{firewall,nat}_policy, providing clear context on when to use it. However, it does not include explicit exclusions or prerequisites.

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