domains_get_nameservers

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

The description adds no behavioral context beyond the readOnlyHint annotation. It does not disclose potential edge cases (e.g., unknown domain handling), rate limits, authentication requirements, or any other operational details. The annotation already covers the read-only nature, so the description provides no additional value here.

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, front-loaded sentence: 'Get nameservers for a domain.' No extraneous words, and it directly states the action and target. This is appropriately concise for a simple tool.

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 read tool with one parameter, readOnlyHint, and an output schema, the description is largely complete. It clearly states the purpose, and return values are covered by the output schema. Minor missing context includes error behavior, but not critical for the basic operation.

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?

The schema fully documents the sole parameter 'domain' with an example format, achieving 100% coverage. The tool description simply says 'for a domain' which adds no new meaning beyond the schema. Baseline of 3 is appropriate since schema handles parameter semantics.

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 'Get nameservers for a domain' uses a specific verb and resource, clearly indicating this is a read operation to retrieve nameserver information. It distinguishes itself from sibling tools like 'domains_update_nameservers' (write operation) and 'dns_get' (DNS records), making the purpose 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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, expected outcomes, or exclusion scenarios. The intended usage must be inferred entirely from the tool name and one-line description.

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