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

With no annotations, the description carries the full burden. It usefully flags the mutation ('Mutating.') and discloses that DS propagation to the parent delegation is handled server-side, which is real behavioral context. However, it omits auth/permission requirements, reversibility, and the effect of disabling, so it only partially compensates.

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?

A single front-loaded sentence with the action first and the server-side caveat parenthetical, plus a terse 'Mutating.' flag. No wasted words, though the one-word sentence is a slight stylistic outlier.

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 two-parameter mutation toggle with no annotations and no output schema, the description covers what the tool does, that it mutates, and the DS-propagation side effect. It still leaves auth requirements and disable-side behavior unstated, so it is adequate but not fully 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 0% and no annotations exist, so the description must compensate. It conceptually covers both parameters ('your zone' maps to zoneId, 'enable or disable' maps to the enabled boolean), but adds no format or constraint detail (e.g. UUID requirement) beyond the obvious mapping.

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?

States a specific verb pair and resource: 'Enable or disable DNSSEC signing for your zone'. This is clearly distinct from zone/record siblings (dns_zone_create, dns_record_update), so an agent can route to it without opening the schema, though it does not explicitly name a sibling to contrast with.

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 the operation (toggle DNSSEC signing) but gives no explicit when-to-use guidance, no prerequisites, and no mention of alternatives or the conditions that select this tool over adjacent zone tools.

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