Enable or disable DNSSEC signing on a zone

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

Beyond the annotations, the description discloses that the tool returns nothing on success and warns that stopping signing while a DS record is published can cause validation failures. This is meaningful behavioral context not inferable from readOnlyHint=false or destructiveHint=false, and it does not contradict any annotation.

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 sentences with no filler: the action comes first, then the critical usage distinction, then the risk warning. Every sentence earns its place and the most decision-relevant caveat is included without bloating the description.

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 an output schema, two fully documented parameters, explicit sibling differentiation, and a warning about failure conditions, the description is complete for safe and correct invocation. No material gap remains for an agent deciding whether and how to use this tool.

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% and both parameters already have inline descriptions. The description still adds value by clarifying that domainName means a zone hosted here and by linking enabled to the start/stop behavior, which strengthens an agent's understanding beyond the raw schema.

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 ('Starts'/'stops') with a clear resource ('DNSSEC signing of a zone') and explicitly distinguishes itself from eurodns_domain_set_dnssec. An agent can immediately tell what the tool does and how it differs from a similarly named sibling.

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 boundaries: use it only for domains registered elsewhere, and for domains registered here use eurodns_domain_set_dnssec instead. It also references eurodns_dns_get_dnssec_status for checking state, giving the agent a clear decision path.

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