Get DNS snapshot list

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

Annotations already mark this as read-only and non-destructive. The description adds the context that this lists backup points for restoration, but it does not disclose additional behavioral details such as sort order, pagination, or what snapshot metadata is returned.

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 two short sentences with no filler. The core operation is front-loaded, and the second sentence adds practical usage context without redundancy.

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 read-only list operation with one well-documented parameter, the description is largely complete. It clearly indicates the tool's role in the restoration workflow, though the absence of an output schema means it does not describe the exact return shape.

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?

The single 'domain' parameter has 100% schema description coverage, so the schema fully documents it. The description does not add extra format or meaning beyond 'domain', which is adequate but not enhanced.

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 states a clear verb and resource: 'Retrieve DNS snapshots for a domain.' The phrase 'view available DNS backup points for restoration' adds purpose and helps distinguish this from snapshot restoration tools, though it does not explicitly name or differentiate from sibling DNS_getDNSSnapshotV1.

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 gives a clear usage context: use this endpoint to view available DNS backup points before restoration. It does not explicitly say when not to use it or name alternatives, but the restoration-focused framing provides enough guidance for an agent.

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