Get WHOIS profile

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only a small amount of context by specifying that the profile contains domain registration contact information; it does not disclose response structure, which profiles are retrievable, or any authentication/prerequisite details.

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 filler. The core action is front-loaded, and the clarifying use-case sentence earns its place by explaining what the returned data represents.

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 one-parameter read-only tool with no output schema, the description is mostly sufficient: it names the resource, explains the data in plain terms, and the required whoisId parameter is straightforward. Slightly more explicit distinction from the profile-list sibling would make it fully complete.

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%: the sole parameter whoisId is already documented as 'WHOIS ID'. The description does not add any extra meaning about the parameter format, where to find the ID, or how it relates to a profile, so the schema carries the full explanatory burden.

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 states a specific verb and resource: it retrieves a WHOIS contact profile and clarifies this is domain registration contact information. It is distinguishable from sibling list/update/delete tools at a basic level, though it does not explicitly contrast with domains_getWHOISProfileListV1 or explain that it fetches a single profile by ID.

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 says 'Use this endpoint to view domain registration contact information,' which gives a clear use case. However, it does not mention when not to use it or point to alternatives such as domains_getWHOISProfileListV1 for listing profiles, so the routing guidance is implied rather than explicit.

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