Delete DNS Zone RRSet

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

Annotations already declare destructiveHint=true (permanent deletion). The description reinforces this with 'permanently' and adds the condition about change protection. While it doesn't detail error behavior if protected or permissions needed, it provides useful context beyond annotations 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?

Description is extremely concise with only two sentences. It front-loads the purpose and adds a critical condition. Every word is necessary; no fluff. Structure is optimal for quick parsing.

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 simple delete tool with no output schema and clear annotations, the description covers the essential action and a key precondition. It lacks explicit mention of what happens if the RRSet doesn't exist or post-deletion state, but given the straightforward nature, it is largely 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% and all parameters have descriptions in the schema. The description adds no additional parameter details beyond what is already in the input schema, so it meets the baseline but does not enhance parameter understanding.

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?

Description clearly states the action: delete an RRSet from a DNS zone permanently. It specifies the resource (RRSet), the operation (delete), and a key condition (not change-protected). This distinguishes it from siblings like hetzner_delete_zone (deletes entire zone) and hetzner_create_zone_rrset (creates instead).

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?

Description explicitly states a precondition: 'The RRSet must not be change-protected.' This provides clear guidance on when the tool can be used. However, it does not explicitly state when to avoid this tool or mention alternatives, but the context of deleting a specific RRSet is implied from the name and sibling tools.

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