ncloud_dns_rollback_domain

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

The description includes a warning emoji and labels the operation as 'Destructive,' adding context beyond the annotations (destructiveHint: true). It clearly states that pending changes will be discarded, which is not conveyed by the annotation alone. The description does not contradict 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 a single, front-loaded sentence that communicates the purpose, effect, and requirement without extraneous words. It starts with a visible warning emoji and uses minimal yet complete language.

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 tool with two parameters, no output schema, and destructive annotations, the description covers the essential: what it does (rollback), the effect (discard pending changes), and the execution requirement (confirm=true). It lacks details on the rollback target (e.g., the state after the last apply), but that is likely implied by domain management context. Overall, it is sufficient for an agent to understand the tool's behavior.

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 the schema already documents the parameters. The description reiterates the confirm parameter's role ('Set confirm=true to execute'), which is helpful but adds little beyond the schema's description of confirm as a boolean with default false. The domainId parameter is not discussed further, which is adequate given its straightforward type.

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 specific action ('Rollback'), the resource ('Global DNS domain'), and the effect ('to the previously applied state. Pending changes will be discarded.'). It effectively distinguishes this tool from siblings like ncloud_dns_apply_domain, which applies pending changes.

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 warns that pending changes will be discarded and requires confirm=true to execute. This provides clear guidance on when to use (rolling back) and the necessary caution. While it doesn't explicitly state when not to use it, the context of destructive operations and the confirm parameter serve as sufficient usage guidance.

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