ncloud_list_groups

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

The readOnlyHint annotation already indicates a safe read operation. The description adds the context 'for managing sub account permissions' but does not disclose pagination behavior, result ordering, or the meaning of 'all' given the page/size parameters. It does not contradict 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, front-loaded sentence with no unnecessary words. It immediately communicates the tool's action and resource, making it highly 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?

For a simple read-only list tool with two well-documented parameters and a readOnlyHint annotation, the description is sufficiently complete. It clearly states the tool's purpose, though it could mention what the return data would include or clarify that 'all' may require pagination.

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 100% with clear descriptions for 'page' ('Page number (0-based, default: 0)') and 'size' ('Page output count (default: 10)'). The description adds no additional parameter semantics beyond the schema, so the baseline 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 'List all IAM groups for managing sub account permissions' uses a specific verb ('List'), a clear resource ('IAM groups'), and adds context about sub account permissions. It clearly distinguishes from related tools like ncloud_create_group or ncloud_delete_group, though it does not explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives, such as when to use ncloud_list_sub_accounts or ncloud_list_policies. There are no exclusions, prerequisites, or explicit use-case scenarios mentioned.

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