Get DNS Snapshots

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

No annotations are present, so the description must carry the full transparency burden. It only says 'List DNS snapshots', which implies a read-only operation, but does not state this explicitly, nor does it disclose output format, pagination, or any side effects. This is insufficient for a tool without annotation support.

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, clear sentence with no redundant words. It is appropriately compact and front-loads the action verb, making it easy to scan.

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?

With no output schema and no annotations, the description is too sparse to be contextually complete. It doesn't describe the structure of the returned list, how snapshots are identified, or how this tool relates to dns_get_snapshot and dns_restore_snapshot, leaving the agent under-informed.

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 schema provides 100% coverage for the only parameter, 'domain', described as 'Domain name'. The description adds no additional parameter semantics beyond restating that snapshots are for a domain, so the baseline score of 3 applies.

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 the verb 'List' with the resource 'DNS snapshots' and scope 'for a domain', clearly indicating a listing operation. However, it does not explicitly distinguish itself from the sibling tool dns_get_snapshot, relying only on pluralization to imply it lists all snapshots versus retrieving one.

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?

No explicit when-to-use or alternative guidance is provided. The description implies the tool is for listing snapshots, but it doesn't mention related tools like dns_get_snapshot or dns_restore_snapshot, leaving the agent without clear direction on tool selection.

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