sdcloud_list_nat_policy_rule_groups

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

With no annotations, the description should disclose behavioral traits like pagination, filtering, or required policy_id. It only states 'List rule groups within a NAT policy,' adding no behavioral context beyond the input schema, which already documents parameters.

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 short sentence that is concise and front-loaded with the verb. It lacks additional structured details but earns points for brevity.

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 output schema and only one sentence, the description is incomplete. It does not explain what the tool returns, pagination behavior, or how to use filters. The schema provides param details, but overall context is lacking.

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 description coverage is 83%, so the baseline is 3. The description does not add parameter meaning beyond what the schema provides (e.g., policy_id required, pagination params).

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 lists rule groups within a NAT policy using specific verb (list) and resource (rule groups). It is unambiguous but does not explicitly differentiate from sibling tools like sdcloud_list_nat_policy_rules or sdcloud_create_nat_policy_rule_group.

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?

No guidance is provided on when to use this tool versus alternatives, such as listing rules or creating rule groups. There is no mention of prerequisites, when not to use, or context for invoking.

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