sdcloud_list_nat_policies

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

No annotations are provided, so the description carries the full burden. It mentions pagination, filtering, and sorting but does not disclose whether the operation is read-only, requires special permissions, or returns detailed or summary information. The behavioral disclosure is minimal.

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 directly front-loaded. It is efficient but could be more informative without increasing length. No 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?

Given no output schema and many sibling listing tools, the description is insufficient. It does not explain the return format, pagination limits, filter syntax, or how this list differs from other NAT policy list tools. The completeness is low for the tool's complexity.

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?

All five parameters are described in the schema (100% coverage). The description summarizes the parameters as 'optional pagination, filtering, and sorting', but does not add new insights beyond the schema. Baseline score of 3 is appropriate as the description does not degrade or enhance parameter understanding.

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 (List) and resource (NAT policies) with additional behavior (optional pagination, filtering, sorting). However, it does not differentiate from sibling list tools like 'sdcloud_list_nat_policy_rules' or 'sdcloud_list_nat_policy_hierarchy', which list related but distinct resources.

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 on when to use this tool versus alternatives such as 'sdcloud_list_nat_policy_rules' or 'sdcloud_get_nat_policy'. No prerequisites, exclusions, or context for selection are provided.

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