domains_getWHOISProfileListV1

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

No annotations exist, so the description must disclose all behavioral traits. It correctly indicates a read operation via 'Retrieve', but omits details such as idempotency, required permissions, rate limits, or that no data is modified. The description is too sparse to fully inform an agent beyond the basic action.

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 consists of two concise sentences, front-loading the action and adding context. Every word is necessary; no redundancy or excessive detail. It is appropriately sized for the tool's simplicity.

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 lack of an output schema, the description should hint at the return format or fields. It merely states 'WHOIS contact profiles' without specifying that it returns a list, possible pagination, or what fields each profile contains. The tool's complexity is low, but the description remains incomplete for an agent to fully understand the result.

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 one parameter 'tld' described. The description adds no additional meaning or usage constraints beyond the schema's description. Since the schema already explains the parameter, the description's minimal contribution aligns with the baseline score of 3.

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 'Retrieve WHOIS contact profiles', which specifies the action (retrieve) and resource. It implies a listing operation, distinguishing from siblings like create and delete. However, it does not explicitly differentiate from domains_getWHOISProfileV1 (single profile retrieval), leaving slight ambiguity.

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 advises to 'use this endpoint to view available contact profiles for domain registration', providing basic usage context. It does not specify when not to use it, nor mentions alternatives like the single profile endpoint. The optional TLD filter is not described, leaving usage guidance implicit.

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