Get the DNSSEC status of a zone

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

Annotations already mark the tool as read-only and non-destructive. The description adds value beyond those hints by stating exactly what it returns (DNSSEC-signed status, keys, DS data) and by flagging a temporal behavior: checking before DNSEC mutations and after nameserver changes.

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 front-loaded sentences contain no filler. The first sentence states the tool's function and output; the second provides actionable usage guidance. Every sentence 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 single-parameter, read-only, idempotent tool with an output schema, the description is complete. It covers what the tool reports, what data it returns, and when to use it, leaving no critical gap for correct invocation.

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 input schema covers the sole parameter fully, defining domainName with an example and clarification that the domain's DNS must be hosted here. The description adds no extra parameter-level meaning, so the baseline 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 states a specific action and resource: 'Reports whether the zone is DNSSEC-signed and returns its keys and DS data.' This clearly distinguishes the tool from the many DNS-related siblings by focusing on DNSSEC status, keys, and DS data rather than general zone records or profiles.

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 explicit usage timing: check before eurodns_dns_set_dnssec or eurodns_domain_set_dnssec, and again after changing nameservers. This is clear context, though it does not explicitly exclude alternatives among the other DNS get tools.

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