combell_domains_set_nameservers

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

The description explicitly discloses a side effect: DNS resolution will switch to the new name servers after propagation. The annotations already indicate idempotentHint=true and destructiveHint=false, and the description adds behavioral context about the propagation delay and the fact that this replaces existing nameservers. It does not over-explain and directly warns about the operational impact.

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?

The description is a single sentence that communicates the core action and the important side effect. It is concise, front-loaded, and contains no filler or redundant restating of 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?

Given that the tool has only two parameters and no output schema, the description is reasonably complete: it names the action, the affected resource, and the propagation effect. It could mention the required format for domain_name or the exact semantics of replacing nameservers (e.g., that existing nameservers are overwritten), but overall this definition provides enough context for an AI agent to call the tool correctly with minimal assumptions.

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 50%, meaning the name_servers parameter has a description, but domain_name has none. The description clarifies that the name_servers array is a full replacement list ('Replace'), which adds meaning to the operation mode. Still, it could state the required format for domain_name (e.g., bare domain vs with www) to improve parameter semantics further.

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 (Replace) with a clear resource (name servers of a domain name). It accurately distinguishes this tool from siblings like combell_dns_records_update and combell_domains_get, because it targets domain-level nameserver configuration rather than individual DNS records. The scope is unambiguous.

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 implies usage: use this when you need to change which name servers serve a domain. It does not explicitly state when not to use it, nor does it mention alternatives such as combell_dns_records_create/update for managing individual records instead of delegated nameservers. Some guidance is present, but exclusions and alternatives are absent.

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