ncloud_resource_list_groups

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

The readOnlyHint=true annotation already communicates that this is a safe read operation, and the description is consistent with it ('List...'). It adds minor behavioral context by mentioning filtering and pagination, but it does not disclose details such as whether results are capped, ordered, or how pagination behaves at boundaries.

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?

A single front-loaded sentence that conveys the core action, the resource, and the two optional behaviors with no wasted words. The details are appropriately deferred to the input schema.

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 all parameters fully documented in the schema and a readOnlyHint annotation, the description is nearly sufficient. The main gap is that it does not clarify which 'groups' are being listed, which matters given the ncloud_list_groups sibling and the absence of an output schema describing the returned group objects.

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%: page, size, and groupName each have descriptions including defaults, constraints, and exact-match semantics. The description only restates these as 'optional name filter and pagination,' adding no syntax or format detail beyond what the schema already provides.

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 names a specific verb ('List') and resource ('resource groups') and adds the key capabilities of name filtering and pagination. It does not, however, explicitly distinguish this tool from the similarly named sibling ncloud_list_groups, leaving the agent to infer the difference from the tool name.

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?

There is no guidance about when to use this tool or when to prefer an alternative. Given that the sibling ncloud_list_groups also lists 'groups', an explicit note about this being the resource-group tool (vs the IAM/sub-account group tool) would be valuable, but the description offers no such direction.

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