Get domain nameservers

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral detail: Route 53's apex NS set is what you give the registrar, and GoDaddy's v3 API cannot read nameservers back. No contradiction with annotations.

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 sentences that are front-loaded with purpose and then add a useful qualifier. No wordiness or redundancy; every clause contributes.

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 the presence of an output schema and strong annotations, the description covers purpose, provider-specific behavior, and read-only confirmation. It implicitly differentiates from set_nameservers. A minor gap is the lack of explicit guidance on when not to use it, but that is largely covered by the tool's read-only nature.

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 for 'provider' is thorough ('Force a provider instead of routing by domain...'). The 'domain' parameter is self-explanatory. With 50% schema coverage, the description does not compensate further, but it doesn't need to because the existing schema coverage is sufficient for the simple parameters.

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 specific verb 'Show' plus resource 'nameservers for a domain', clearly distinguishing from sibling set_nameservers. It also adds provider-specific nuance (Route 53 apex NS set, GoDaddy limitation) that further clarifies the exact scope.

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 clear context for when to use the tool (reading nameservers for registrar) and notes a key limitation (GoDaddy cannot read back). It does not explicitly name alternatives or exclusions, but the read-only nature is evident from both description and annotations.

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