ncloud_dns_delete_records

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

The description adds behavioral info beyond annotations: 'This permanently removes the specified records' and the requirement for confirm=true. Since annotations already include destructiveHint=true, the description reinforces and provides the exact mechanism for execution.

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 three short sentences. The warning emoji draws immediate attention, and each sentence serves a purpose: declaring destructiveness, specifying permanence, and stating the confirmation requirement. No wasted words.

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 with 3 parameters described fully in schema, the description covers the destructive nature and confirmation gate. It lacks prerequisites (e.g., domain must exist), but the schema and context of sibling tools likely compensate. Overall complete enough for its complexity.

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 baseline is 3. The description only adds significance to the confirm parameter by stating it must be true to execute. Other parameters (domainId, recordIds) are already well-described in the schema, so no additional value is needed.

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 (delete) and resource (DNS records) with the phrase 'Delete DNS records from a Global DNS domain'. It distinguishes from sibling tools like ncloud_dns_list_records and ncloud_dns_create_records by being explicitly destructive.

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 a key usage guideline: 'Set confirm=true to execute', which is essential for a destructive operation. It implicitly tells the agent when to use this tool (when deletion is intended) but does not explicitly mention when not to use it (e.g., for updates, use ncloud_dns_update_records).

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