ncloud_ncr_delete_registry

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

The description adds value beyond the destructiveHint annotation by specifying that the deletion is permanent and requires the confirm parameter. It also reinforces the destructive behavior. No contradictions with annotations.

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, consisting of one sentence plus a warning emoji. It front-loads the destructive nature and the key requirement. Every word is necessary and no information is wasted.

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?

The description is adequate for a simple destructive operation with two parameters, but lacks details on what happens when confirm is false (e.g., no-op) and does not explicitly state irreversibility beyond 'Permanently delete'. No output schema, so return behavior is unclear.

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 baseline is 3. The tool description does not add new parameter information beyond what the schema already provides for confirm and registryName. It mentions the confirm requirement but no additional semantics.

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 it deletes a container registry permanently, using a warning emoji and the word 'Destructive'. The purpose is unambiguous and distinct from sibling tools like ncloud_ncr_create_registry or ncloud_ncr_list_registries.

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 instructs to set confirm=true to execute the deletion, which is a key usage guideline. It implicitly warns about destructive nature, but does not explicitly state when not to use it or suggest alternatives. However, the instruction is sufficient for correct invocation.

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