ncloud_create_group

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

Annotations only include destructiveHint=false, which is not contradicted by the description. The description adds the dryRun behavior ('preview without creating'), which is useful. However, it does not disclose other behavioral aspects such as idempotency, required permissions, or what happens if the group already exists, so transparency is adequate but not rich.

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 exceptionally concise at two sentences, with the core purpose front-loaded and no extraneous content. The dryRun hint is a valuable addition that adds useful information without bloat. Every word earns its place.

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 simple (3 params, 1 required, no output schema, no nested objects), and the description plus schema jointly cover purpose, parameters, and the dryRun feature. However, there is no mention of what the response contains or any post-creation effects, which would be slightly more complete. For a basic create operation, this is nearly sufficient, hence a 4.

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% for all three parameters (dryRun, groupName, groupDescription), providing full semantics in the schema. The description does not add extra parameter meaning beyond what the schema already defines, so it neither enhances nor detracts. Baseline 3 is appropriate given the high schema coverage.

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 and resource: 'Create a new IAM group.' This is specific and distinguishes from sibling create tools like ncloud_create_role or ncloud_create_sub_account by naming the resource type 'IAM group.' The additional dryRun hint further clarifies scope without ambiguity.

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 clear context for when to use the tool (to create an IAM group) but does not mention alternatives or exclusions. The dryRun=true hint offers guidance on a parameter, not on tool selection, so it does not fully address usage versus alternatives. No explicit when-not-to-use scenarios are provided.

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