sdcloud_start_policy_preview_job

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

No annotations are provided, so the description carries full burden. It discloses the core behavioral trait: it's a preview that computes a configuration diff without applying changes. It could further describe what happens after the job starts (e.g., how to get results), but the essential behavior is clear.

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 well-structured sentence that front-loads the main purpose, followed by a sibling differentiation. No fluff or redundancy.

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 tool's complexity (bulk preview with an opaque schema body) and lack of output schema, the description is adequate but leaves gaps. It doesn't explain how to format the request body or what the job result looks like. It does differentiate from siblings, but more context would improve agent usability.

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 only parameter is 'body', described as 'JSON request body matching the target Security Director Cloud schema.' This adds no specific meaning beyond the schema, and the schema itself does not define the internal structure of the body. The description does not help the agent understand what fields or format are required.

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 (start a bulk preview job) and the resource (across multiple policies/devices). It distinguishes from sibling single-policy tools by specifying that it operates on all policies in the request body, unlike the single-policy tools.

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 tells when to use this tool (for bulk preview across multiple policies) and contrasts it with single-policy alternatives, providing clear usage guidance.

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