Restore DNS snapshot

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only a restatement of the revert behavior and does not disclose additional consequences such as overwriting current DNS records, but it does not contradict the 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?

Two short sentences convey the action and the reason to use it, with no filler or redundant detail. The action is front-loaded.

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 two-parameter destructive restore with annotations covering the risk profile, the description is nearly complete. A note that the restore overwrites the current DNS configuration or that the snapshot should be obtained from the DNS snapshot list would make it fully complete.

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% and both parameters are documented in the schema ('Domain name' and 'Snapshot ID'). The description adds no additional parameter guidance, matching the baseline for fully covered schemas.

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 uses a specific verb-resource pair ('Restore DNS zone to the selected snapshot') and clarifies with 'revert domain DNS to a previous configuration.' It clearly distinguishes this from DNS_getDNSSnapshotListV1/DNS_getDNSSnapshotV1 and from DNS_updateDNSRecordsV1/DNS_resetDNSRecordsV1.

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?

It gives a direct usage instruction: use this endpoint to revert a domain DNS to a previous configuration. It does not explicitly name alternatives or state when not to use it, so it falls short of 5, but the intended context is clear.

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