set_domain_nameservers

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

With no annotations, description discloses mutation ('Replace'), scope requirement, and plain write nature. Could be more explicit about full replacement vs partial, but 'replace' is clear enough.

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?

Four concise sentences front-loaded with action, covering all key points (function, constraints, source, alternative) without waste.

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 simple tool with no output schema, description covers purpose, constraints, source, and alternative. Slightly missing success indication, but adequate for agent use.

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 clear descriptions. Description adds context (owned domain, scope) but does not significantly enhance parameter meaning beyond schema.

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?

Clearly states 'Replace an owned domain's nameservers', which is a specific verb-resource combination. Sibling mentions like get_domain_nameservers and manage_domain provide differentiation.

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?

Explicitly tells when to use (replace nameservers), where to get id (list_domains), required scope (domains:write), and provides an alternative single-action tool (manage_domain with action:'nameservers').

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