Update Domain Contacts

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

Discloses key behaviors: only provided contact roles are updated (partial update), omitted roles remain unchanged, changing registrant may trigger transfer lock. Adds context beyond annotations (destructiveHint=true) about specific mutation effects and user confirmation requirement.

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?

Every sentence adds value: starts with core action, then prerequisite, warnings, partial update behavior, and user confirmation instruction. Well-structured and no redundant text.

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?

Covers prerequisites, side effects, partial update nature, and user confirmation. Lacks details on error handling for invalid contact IDs, but is sufficient for a mutation tool with destructive annotation and no output schema.

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?

All parameters are described in schema (100% coverage). The description adds important context for registrant parameter (transfer lock warning) and explains overall update behavior (only provided roles updated). This adds value beyond schema descriptions.

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 it updates domain contacts (registrant, admin, tech, billing) using contact IDs, which distinguishes it from sibling tools like save_contact (creates contacts) and get_contact (retrieves).

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 directs to use save_contact first to obtain contact IDs, warns about ICANN 60-day transfer lock on registrant change, and advises to confirm with user before calling. Provides clear when-to-use and preconditions.

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