dnssec_key_rollover

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

With no annotations, the description carries the full transparency burden. It reveals specific detection logic (multiple DNSKEYs, rollover methods, DS matching), which goes beyond the tool name. However, it does not disclose whether this is a read-only operation or if it requires any special access, though the nature of a DNS check implies read-only.

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?

Three concise sentences that front-load the purpose, then detail detection logic in under 30 words. Every sentence adds information.

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 description explains the tool's core purpose and what it reports (rollover method, DS mismatch condition), which partially compensates for the lack of an output schema. However, it does not detail the exact return format or include context on when rollover detection is relevant, leaving some gaps.

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 coverage is 100% for the single 'domain' parameter, which the schema already describes clearly. The description adds no additional parameter semantics beyond what the schema provides.

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 clearly states the purpose: checking for DNSSEC key rollover. It differentiates from sibling DNSSEC tools by focusing specifically on rollover detection and classification, with explicit behaviors like detecting multiple DNSKEYs and flagging DS mismatches.

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 usage for checking DNSSEC key rollover but provides no explicit guidance on when to use this tool versus sibling DNSSEC tools like dnssec_validate or dnssec_check_dnskey. No alternatives or exclusions are mentioned.

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