ncloud_list_sub_accounts

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

The annotation readOnlyHint=true already declares this as a safe read operation. The description adds the organizational scope and clarifies that 'sub accounts' are IAM users, which is useful context. However, it does not disclose pagination behavior, return format, or other behavioral traits beyond what the annotation provides. No contradiction exists.

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 redundant words. Every part contributes meaning: the verb, the resource, and the scope. It is appropriately sized for the simplicity of the tool.

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 listing tool with comprehensive schema descriptions and a read-only annotation, the description is adequate. It does not mention pagination or search capabilities, but these are already documented in the schema. The lack of an output schema is not an issue for a list operation returning a list of sub accounts.

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 input schema provides complete descriptions for all four parameters (page, size, searchWord, searchColumn) with 100% coverage. The tool description itself adds no parameter-specific details, but the schema already documents them clearly, 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 sub accounts (IAM users) in the organization' uses a specific verb ('List'), a clear resource ('sub accounts' / 'IAM users'), and a scope ('in the organization'). It clearly distinguishes from sibling tools like ncloud_get_sub_account_detail (specific account), ncloud_create_sub_account, and ncloud_delete_sub_account by its listing intent.

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 implies that this tool is for listing all sub accounts, but it does not explicitly state when to use it over alternatives such as ncloud_get_sub_account_detail for retrieving a specific account, nor does it mention any exclusions. The context is clear for a straightforward listing operation, but explicit guidance is missing.

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