Get DNS snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds useful context by noting the snapshot contains DNS zone records and serves historical viewing, which clarifies what kind of data is returned without contradicting 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?

The description is two short sentences with no filler. The first sentence front-loads the core action and resource, and the second sentence adds the practical use case. Every phrase earns its place.

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 tool with two clearly described required parameters and no output schema, the description is complete. It explains what the tool returns (DNS zone records from a snapshot) and when to use it, so an agent has enough context to call it correctly.

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 both 'domain' and 'snapshotId' are already documented. The description adds minimal new meaning beyond the schema—only that a 'particular' snapshot is retrieved—so a baseline score of 3 is appropriate.

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 specific verb ('Retrieve') and resource ('particular DNS snapshot'), and clarifies that the result includes the contents of DNS zone records. The word 'particular' distinguishes it from listing all snapshots, and 'view historical DNS configurations' separates it from restore and update operations.

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 when to use this endpoint: 'Use this endpoint to view historical DNS configurations for domains.' It gives a clear use case, but it does not explicitly name alternatives like DNS_getDNSSnapshotListV1 for listing snapshots or DNS_restoreDNSSnapshotV1 for restoring them.

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