ncloud_create_group

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

Annotations already indicate destructiveHint=false, so the description correctly implies non-destructiveness. It adds the dryRun preview behavior, which improves transparency. However, it omits details like what happens on duplicate names or error cases, and there is no mention of permissions required.

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 two sentences long, directly stating the purpose and a key usage hint. No extraneous information. Front-loaded with the primary action.

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 creation tool, the description covers the basic action and dryRun feature. However, it lacks information about the response format (no output schema provided), any constraints, or error handling. This leaves some gaps for an agent to understand the full behavior.

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 coverage is 100%, with each parameter described. The description repeats the dryRun concept from the schema, adding no new semantic value. For groupName and groupDescription, it provides no additional context beyond the schema. Baseline 3 is appropriate given 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 'Create a new IAM group,' specifying the verb and resource. It distinguishes from siblings like ncloud_list_groups and ncloud_delete_group by focusing on creation. The dryRun hint adds precision.

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 explicitly advises using dryRun=true to preview without creating, which provides clear usage context. However, it does not mention prerequisites, limitations (e.g., name uniqueness), or when to use alternatives like updating (no update tool exists for groups). Still, the guidance is helpful for typical use.

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