Create WHOIS profile

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

Annotations already mark this as non-read-only and non-destructive, and the description's 'Create' and 'add new' wording aligns without contradiction. It adds minimal behavioral context—contact profiles are used for domain registration—but does not discuss side effects, relationship to domains, or whether the profile is reusable, which is acceptable given the annotation coverage.

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 two short sentences with no unnecessary filler. The first sentence restates the title, but the second adds useful domain-registration context. It is appropriately sized for a straightforward creation endpoint.

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 has two nested objects with empty property definitions and no output schema, and the description does not specify what whois_details or tld_details should contain. An agent would struggle to construct a valid request body, especially without knowing whether the created profile is automatically tied to a domain or is just a stored reusable profile.

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 coverage is 100%, so the baseline is 3. The description adds only a general hint that 'contact information' is involved, but does not detail the structure of the nested whois_details or tld_details objects, whose schemas are empty. The description does not need to repeat all parameter names, but it adds little beyond the 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?

The description uses the specific verb 'Create' with a clear resource, 'WHOIS contact profile,' and elaborates with 'add new contact information for domain registration.' This clearly distinguishes the operation from sibling WHOIS tools that get, delete, change, or set default profiles.

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 explicitly states when to use the endpoint: 'Use this endpoint to add new contact information for domain registration.' It provides clear context for the creation action, though it does not name alternative tools or explicitly exclude updating or deleting existing profiles.

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