ncloud_delete_role

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

Beyond the annotations (destructiveHint=true), the description adds critical behavioral detail: the operation is 'permanently' destructive and requires explicit confirmation to execute. This enhances the agent's understanding of consequences and safeguards.

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 conveys the destructive nature, the target resource, and the execution requirement. Every word earns its place, making it highly efficient.

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 delete operation, the description covers purpose, parameter requirement, and safety warning. It does not mention potential side effects on dependent resources, but these are not explicitly requested and the annotation already flags destructiveness, making it sufficiently 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?

The input schema already provides full descriptions for both parameters (roleNo and confirm), covering 100% of parameter semantics. The description's mention of 'confirm=true' duplicates the schema's explanation without adding new meaning, so it stays at the baseline.

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 ('Permanently delete') and the resource ('IAM role'), making it unambiguous. It also distinguishes itself from sibling tools like ncloud_create_role and ncloud_list_roles by specifying deletion.

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 usage context by warning 'Destructive' and requiring 'confirm=true to execute'. It lacks explicit alternatives or when-not-to-use guidance, but the context is sufficient for an agent to know this is the deletion tool.

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