edit_dnssec

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

The description adds significant context beyond annotations by disclosing the dual preview/execute mode based on the confirm parameter. Annotations already cover idempotency and non-destructiveness, and the description complements them without contradiction.

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 description is two sentences with zero fluff, front-loading the primary action and immediately following with critical usage gate 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 covers the core action and the preview/execute distinction. It lacks details on prerequisites (e.g., zone existence) and output format, but given the tool's simplicity and lack of output schema, it is reasonably complete.

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%, so baseline is 3. The description does not add new semantic meaning beyond what the schema already provides for each parameter; it merely restates the confirm gate in prose.

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 'Enable or disable DNSSEC for a zone' with a specific verb and resource, clearly distinguishing it from siblings like get_dnssec (read-only) and zone creation/deletion tools.

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?

It clearly explains the confirm:true gate and the preview behavior, guiding when to execute vs. preview. However, it does not explicitly mention alternatives like get_dnssec for reading the current state, though implied by sibling context.

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