Get Domain Nameservers

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Get nameservers' without indicating whether this is a fast read operation, if it requires specific permissions, or how it behaves with invalid domain IDs. The lack of detail limits transparency.

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, concise sentence that immediately conveys the tool's purpose. There is no extraneous information, making it efficient for quick understanding.

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?

The tool is simple with one parameter, but the description lacks information about the return value (e.g., format of nameservers, whether it returns an array or string). Without an output schema, the description should clarify the response structure, which it does not.

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% with 'domainid' described as 'Domain ID'. The description does not add any additional meaning beyond the schema. Since the schema already explains the parameter, a baseline score of 3 is appropriate.

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 clearly states the action ('Get') and the resource ('nameservers for a domain'), and the tool name matches. It distinguishes from sibling tools like whmcs_update_domain_nameservers, indicating a read-only purpose. However, it does not specify what exactly is returned (e.g., list of nameservers or primary nameserver).

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?

No guidance is provided on when to use this tool versus alternatives like whmcs_get_domain_whois or whmcs_get_client_domains. There is no mention of prerequisites (e.g., domain must exist) or context for best use.

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