sdcloud_cleanup_nat_policy

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

No annotations are provided, and the description only says 'Trigger a cleanup job' without disclosing behavioral traits such as whether the job is asynchronous, what side effects occur (destructive cleanup), or how to monitor job progress. This is insufficient for a tool that initiates a background operation.

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 two sentences with no unnecessary words. The first sentence states the action and target, the second adds a key requirement. Clean 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?

Given no annotations, no output schema, and the complexity of triggering a cleanup job, the description is incomplete. It does not mention that the tool likely returns a job ID for tracking, nor does it connect to associated job-status tools (e.g., sdcloud_get_policy_cleanup_job). The body schema is vague, and cleanup_mode values are not enumerated.

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 50% (body has a description, policy_id does not). The description adds that body requires cleanup_mode (e.g., STRICT), which provides meaningful guidance for the body parameter. However, it does not explain policy_id, and the body's dynamic schema is not elaborated beyond the example.

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 triggers a cleanup job for unused objects/rules referencing a NAT policy. It distinguishes from the sibling tool 'sdcloud_cleanup_firewall_policy' by specifying 'NAT policy' instead of firewall policy.

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 indicates that the body requires a cleanup_mode (e.g., STRICT), giving a hint about usage. However, it does not explicitly state when to use this tool versus alternatives (e.g., deleting a NAT policy directly) or when not to use it. No mention of prerequisites or post-cleanup steps.

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