ncloud_get_acg_rules

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

The annotation readOnlyHint=true already signals a safe read operation, and the description adds the scope of returning all inbound and outbound rules. It does not disclose additional behavioral details such as pagination, ordering, or any default filtering beyond what the schema already states. The description is consistent with the annotation.

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, concise sentence that front-loads the main action and resource. Every word is useful and there is no redundancy or extraneous information.

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?

The tool is a simple read-only list operation with a well-specified schema and clear annotation. The description, combined with the schema, is sufficient for an agent to invoke the tool, though it does not explain return formatting or potential edge cases. Given the simplicity, this is acceptable.

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 all parameter meanings with descriptions (accessControlGroupNo and accessControlGroupRuleTypeCode with its default). The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 verb 'List' and the resource 'all inbound and outbound rules for a specific ACG', which distinctly identifies the tool's purpose. It differentiates from sibling tools like ncloud_list_acgs (listing ACGs) and ncloud_get_acg_detail (getting ACG details) by focusing on rules.

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 usage context is implied: it is used to retrieve firewall rules for a particular ACG, requiring the ACG identifier. However, there is no explicit guidance on when to use this tool versus alternatives like ncloud_list_acgs or ncloud_get_acg_detail, and no mention of exclusions or prerequisites.

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