Delete domain parent DS

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds two useful pieces of context beyond the annotations: the operation is queued (asynchronous) and requires the domains:manage scope. It falls short of 5 because it doesn't describe what happens after queuing or how to track completion.

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?

Two tightly written sentences with no filler, front-loading the action and resource before the permission requirement. Every clause earns its place.

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 destructive mutation, annotations carry the safety profile, the schema fully documents all params, and the description adds the async/queued nature and required scope. Lacking an output schema, it doesn't explain the returned queued action or how the agent should await completion, which keeps it just shy of 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 description coverage is 100% and all three parameters (ds, domain_id, idempotencyKey) are documented in the schema itself. The description adds no syntax or format detail beyond what the schema provides, 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?

States a specific verb and resource: 'Queue deleting DNSSEC DS records at the parent zone for an owned domain.' This is immediately distinguishable from its sibling add_domain_parent_ds by the add/delete verb, and the 'parent zone' scoping is precise.

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 states the auth prerequisite (domains:manage when using an API key) but gives no explicit when-to-use guidance or route to alternatives such as get_domain_parent_ds or add_domain_parent_ds. Usage is implied by the name but not spelled out.

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