sdcloud_start_policy_deploy_job

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

No annotations provided, so description must carry the full burden. It mentions bulk operation and body structure but lacks details on asynchronicity, return value, permissions, or destructive nature. Adequate but not comprehensive.

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 sentences, front-loaded with the core purpose. No redundant information; every word earns its place.

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?

No output schema, so description should clarify what the tool returns (e.g., job ID) and whether it's synchronous. Lacks these details, reducing completeness for a job-starting tool.

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?

Single parameter 'body' with generic schema description. The description adds value by specifying typical body content ('list of policy_ids and/or device_ids'), which aids agent in constructing the request.

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 deploy job across multiple policies/devices, and contrasts with single-policy tools. The verb 'start' and resource 'bulk deploy job' are specific and distinct.

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?

Explicitly contrasts with single-policy tools (sdcloud_{deploy,preview,cleanup,selective_deploy}_{firewall,nat}_policy), specifying when to use this tool for bulk operations vs alternatives. Includes hint about body content.

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