bunny_get_dns_zone

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond annotations by disclosing the scope of the returned data (records, nameserver config, SOA, DNSSEC status), which is meaningful context for a tool with no output schema. It does not contradict the annotations — 'Retrieve' aligns with the read-only hints.

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?

A single sentence that front-loads the primary action and retrieval key, then appends the payload scope in one efficient clause. There is zero wasted wording and every segment 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 one-parameter read-only tool with robust annotations, the description is nearly complete: it states the resource, the key, and the response composition. Minor gaps are the absence of not-found/error semantics and not pointing to bunny_list_dns_zones as the source for obtaining the ID.

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%: the id parameter is already documented as 'DNS Zone ID' with an exclusiveMinimum of 0. The description's 'by ID' adds no new semantic information about the parameter beyond what the schema provides, so the baseline 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 a specific verb ('Retrieve'), resource ('DNS zone'), and retrieval key ('by ID'), then enumerates the returned payload (DNS records, nameserver configuration, SOA settings, DNSSEC status). This clearly distinguishes it from siblings like bunny_list_dns_zones (which enumerates zones without an ID) and bunny_get_dns_statistics (which returns metrics, not zone configuration).

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 implies clear usage context: call this when you hold a DNS zone ID and want the full zone configuration. The enumerated return contents signal what kind of requests this tool serves, but it never explicitly names alternatives (e.g., 'use bunny_list_dns_zones to find the ID first') or states when not to use it.

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