sdcloud_create_nat_policy_rule

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

With no annotations, the description carries the full burden. It only says 'Create,' implying mutation, but provides no details on reversibility, permissions, idempotency, or side effects. This is minimal behavioral disclosure for a creation tool.

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 efficiently communicates the core purpose and a brief parameter hint without any wasted words.

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 tool with a complex nested object parameter and no output schema, the description gives a reasonable overview of the rule's purpose and typical fields. However, it lacks information about the return value (e.g., created rule object) and any constraints on the body.

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 schema covers 50% of parameters (policy_id described, body described generically). The description adds value by listing typical body fields (name, description, nat_type, etc.), going beyond the generic schema description. However, it does not specify required body fields or format.

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 ('Create a rule') and the location ('directly under a NAT policy, not inside a rule group'), distinguishing it from sibling tools like sdcloud_create_nat_policy_rule_in_group. It also hints at typical body fields, reinforcing the purpose.

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 contrasts with creating a rule in a rule group, giving clear when-to-use guidance. However, it does not elaborate on prerequisites (e.g., the NAT policy must exist) or when to avoid this tool.

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