Delete a DNS zone profile

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds important context: the deletion is permanent, no snapshot exists for restoration, and success returns nothing. This helps the agent set user expectations and take caution. There is no 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?

Three sentences front-load the core action and result, then add the risk caveat and the sibling alternative. No filler; each sentence contributes useful decision guidance.

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 one well-schemaed parameter, strong annotations, and an output schema, the description covers the outcome, the irreversibility, the prerequisite check, and the alternative tool—enough for an agent to call it correctly.

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?

The single parameter is fully documented in the schema (100% coverage), including how to obtain the id. The description references the id but introduces no new parameter semantics beyond the schema, so baseline 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?

The description uses a specific verb ('Deletes'), names the resource ('zone profile'), and qualifies the action as permanent. It also distinguishes itself from siblings by explicitly routing edit operations to eurodns_dns_save_zone_profile and verification to eurodns_dns_get_zone_profile.

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 tells the agent to first confirm the id and contents with eurodns_dns_get_zone_profile, and explicitly says to use eurodns_dns_save_zone_profile when the intent is to change rather than remove. This is explicit when/when-not guidance.

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