ncloud_cm2_delete_domain

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

Beyond the destructiveHint/idempotentHint annotations, the description discloses the confirmation gate, the public-zone-only limitation, and a non-obvious auth requirement (main-account API key, HTTP 403 for Sub Account keys, verification note). These are exactly the operational facts annotations cannot carry.

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?

Front-loaded with the destructive warning, then confirmation, scope, and auth constraints in order of importance. The trailing verification anecdote ('verified 2026-10-02 with NCP_ADMINISTRATOR') is useful for trust but is the one element that could be trimmed.

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 parameter-light destructive tool with no output schema, the description covers everything an agent needs: what is destroyed, the confirmation gate, the scope limit, and the credential requirement.

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 description coverage is 100%, so both dmnId and confirm are already documented in the schema. The description restates the confirm=true requirement but adds no format or sourcing detail beyond it, matching the baseline 3 for schema-covered parameters.

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?

Specific verb+resource ('Delete a registered domain') scoped to a named product (Certificate Manager 2.0), which cleanly separates it from siblings like ncloud_cm2_list_domains and ncloud_cm2_register_domain.

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?

Gives a concrete execution precondition ('Set confirm=true to execute') and a scoping constraint ('Public zone only'), which tells the agent when the call is valid. It does not, however, name an alternative operation for other cases (e.g. deactivation), so it stops short of full routing guidance.

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