ncloud_list_groups

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

The description does not contradict annotations (readOnlyHint: true), but it adds no extra behavioral context beyond stating the action. It does not mention pagination behavior, rate limits, or that 'all' groups might be subject to pagination (though schema indicates page/size). With annotations covering readonly, a score of 3 is appropriate.

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 sentence that is clear, direct, and contains no extraneous information. Every word serves a purpose.

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 standard list tool with pagination parameters and no output schema, the description provides the essential purpose but lacks details on return format, default page size, or whether results are sorted. It is adequate but not comprehensive.

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 100%, so baseline is 3. The description does not add any additional meaning to the 'page' and 'size' parameters beyond what is already in the schema. It simply restates the overall purpose.

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 the resource ('IAM groups'), and specifies the context ('for managing sub account permissions'). It distinctly separates this tool from siblings like ncloud_create_group or ncloud_list_sub_accounts.

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 it is for listing IAM groups, but does not provide explicit guidance on when to use it vs alternatives (e.g., ncloud_list_sub_accounts for sub-accounts, or ncloud_create_group for creation). The context is clear but lacks when-not-to-use advice.

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