ncloud_create_role

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

Annotations already declare destructiveHint=false, and the description adds the dryRun behavior. No contradictions. However, it does not disclose other behavioral traits such as whether the role is immediately active, uniqueness constraints, or side effects beyond creation.

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 extremely concise with only two sentences, no redundant information, and front-loads the core purpose. Every sentence adds value.

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?

While the tool has a moderate complexity (6 params, 3 required) and no output schema, the description does not explain what the response contains (e.g., the created role details) or any constraints like roleName uniqueness. It is minimally sufficient but could be more complete.

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%, so parameters are fully described in the schema. The description adds no additional semantic meaning beyond what is already in the schema (e.g., it mentions dryRun but that is also in the schema description). Baseline score 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' and the resource 'IAM role', using a specific verb and noun. It distinguishes from siblings like 'ncloud_list_roles' and 'ncloud_delete_role' by focusing on creation.

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 mentions using dryRun=true for preview, which is a helpful guideline, but it does not specify when to use this tool versus alternatives or any prerequisites (e.g., permissions). It lacks explicit when-not or alternative tool context.

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