ncloud_create_group

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

The annotation only includes destructiveHint: false, which is consistent with creation. The description adds meaningful behavioral context beyond annotations: it explicitly discloses that groupDescription is ignored (a quirk) and explains the dryRun behavior for previewing. This helps an agent anticipate side effects and avoid confusion, significantly enhancing transparency.

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 very concise, consisting of three short sentences that front-load the core purpose ('Create a new IAM group') followed by essential usage notes (no description field, use tags; dryRun for preview). Every sentence adds value with no redundancy or filler.

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 straightforward create operation with 4 parameters, the description covers the key contextual aspects: the resource type, the description field limitation (with recommended workaround), and the dryRun mode. The absence of an output schema is not critical since the description doesn't need to explain return values. It lacks an explicit note that groupName is required, but the schema already indicates this.

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 comprehensive descriptions for all four parameters (100% coverage), including detailed explanations for groupName, tags, dryRun, and the ignored groupDescription. The description reinforces the tag usage and dryRun preview, but adds little beyond what the schema already states. Since schema coverage is high, baseline of 3 is appropriate.

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: 'Create a new IAM group.' It specifies the resource type (IAM group) and the verb (create). It also highlights a key attribute (no description field) that distinguishes this specific group creation from similar tools in other services. With no other create_group sibling, purpose is unambiguous and differentiated.

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 direct usage guidance: it instructs to use tags instead of description (since groups lack a description field) and recommends dryRun=true for previews. However, it does not explicitly mention when not to use this tool or compare it to alternative tools (e.g., listing groups or attaching policies). Given the absence of a direct alternative, this is clear and actionable.

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