ncloud_delete_group

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

Description adds the 'permanently delete' context beyond the destructiveHint annotation, and mentions the confirm flag requirement. However, it does not mention idempotency (annotated as idempotentHint true) or consequences of using confirm=false. Still adds value.

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?

Extremely concise—one short sentence with a warning icon. No wasted words, front-loaded the key information (destructive and confirm requirement).

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 delete operation with annotations covering destructive and idempotent hints, the description is fairly complete. It lacks mention of return values (no output schema) and specifics about behavior when group has dependencies, but overall sufficient.

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 has 100% coverage with clear parameter descriptions. The description adds minimal extra meaning beyond the schema (e.g., 'Set confirm=true to execute' is already in schema). 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?

Description clearly states the verb (delete) and resource (IAM group) with a destructive warning. It distinguishes from sibling tools by specifying it's for IAM groups and requires confirmation.

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?

Explicitly states that confirm=true is required to execute. Provides clear context for using the tool, though it doesn't explicitly list when not to use or alternatives. Since the resource is unique among siblings, this is adequate.

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