delete_dns_subdomain

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so 'DESTRUCTIVE' is largely redundant. The genuinely additive content is the stated pdns/edit authorization requirement and the underlying API endpoint reference, which the annotations do not convey. It stops short of saying what else is affected (e.g. records under the subdomain) or that the deletion is irreversible.

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 tight fragments with zero filler, front-loaded with the action and resource. Both the DESTRUCTIVE warning and the permission requirement are placed where an agent will see them before parsing parameters.

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 3-parameter destructive call with no output schema, the definition covers purpose, safety flag, required permission, and endpoint. It is nearly complete; only the blast radius of the deletion and any confirmation/lookup requirements are left unstated, which the confirm parameter partially mitigates.

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%: id, confirm and server_id are all documented in the schema, including the 'Must be true to run the operation' semantics for confirm. The description adds no parameter-level detail beyond what the schema already provides, so the 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?

States a specific verb and resource ('Delete a subdomain from the subdomains table') and even names the backing endpoint (pdns/delete_subdomain), so an agent can distinguish it from edit_dns_subdomain or add_dns_subdomain. It does not, however, explicitly contrast itself with the similarly named delete_dns_domain or delete_dns_zone siblings.

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 supplies the prerequisite 'Requires pdns/edit permission', which tells the agent under what conditions the call will succeed. It gives no when-to-use vs when-not guidance and does not route the agent to alternatives such as edit_dns_subdomain or delete_dns_domain.

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