edit_dns_subdomain

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

Annotations already declare this as a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds the auth requirement (pdns/edit), but says nothing about what is mutated, reversibility, or side effects beyond that.

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 compact fragments with no filler; the operation is front-loaded ahead of the permission note. Efficient, though the parenthetical endpoint reference is redundant with the tool name.

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 100% schema coverage and annotations carrying the safety profile, the essentials are present. It remains thin on the actual mutation surface — it never indicates which subdomain fields can be changed — leaving the agent to infer the edit scope.

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%, with id, confirm, and server_id all documented in the schema, so the baseline is 3. The description adds no syntax or constraint detail beyond what the schema already states.

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 (update) and resource (subdomain), which cleanly separates it from the add_/delete_/list_ DNS subdomain siblings. It does not clarify which attributes of the subdomain are editable.

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?

Provides a real prerequisite ('Requires pdns/edit permission'), which is genuine usage context. However, it gives no when-to-use vs alternatives guidance and no exclusions relative to add_dns_subdomain or delete_dns_subdomain.

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