Validate a domain's DNSSEC chain of trust from root to TLD, performing recursive cryptographic checks to confirm the domain is securely signed and trusted.
Performs recursive cryptographic chain of trust validation (Root -> TLD -> Domain) for DNSSEC.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | The fully-qualified domain name to validate (e.g. example.com) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds the recursive, root-to-TLD-to-domain traversal behavior, which goes beyond the name, but it does not disclose whether live DNS queries are made, what happens on validation failure, what the return payload looks like, or any side effects or timeouts.
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 single sentence is economical, front-loaded with the action verb, and contains no filler. It earns its place by conveying the recursive scope and traversal path, though it is arguably too sparse given the absence of annotations and output schema.
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?
The tool has no annotations and no output schema, so the description must compensate, but it only explains the validation mechanism. It omits return format, failure behavior, when to choose this over audit_dnssec_records, and whether network queries are performed, leaving an agent without enough context to call it confidently.
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 the schema already fully documents the single 'domain' parameter with an example. The description adds nothing about parameter semantics beyond the schema, 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 verb ('performs') and resource ('cryptographic chain of trust validation') with an explicit traversal path (Root -> TLD -> Domain). This recursive validation scope clearly distinguishes it from the sibling audit_dnssec_records, which presumably audits records rather than validating the trust chain.
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?
There is no guidance on when to use this tool versus audit_dnssec_records, nor any mention of prerequisites, exclusions, or context (e.g., when DNSSEC validation is appropriate versus auditing record configuration). An agent must infer use cases entirely from the name and the one-line description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.