domains_getWHOISProfileListV1

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the read action. It does not mention whether the operation is read-only, idempotent, requires authentication, or any rate limits. For a tool with no annotations, the description should provide more behavioral context.

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 only two sentences, front-loading the action and adding a brief usage hint. It is concise with no unnecessary words or redundancies.

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 tool has no output schema and only one optional parameter, the description is minimal but adequate. It explains the purpose and suggests a usage context (domain registration). However, it does not describe the output format or any implicit behavior, which leaves some gaps.

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?

The input schema covers the single parameter (tld) with a description. The tool description does not add any additional parameter information beyond what the schema provides. With 100% schema coverage, the baseline is 3, and no extra value is added.

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 the tool retrieves WHOIS contact profiles, and the verb 'view' aligns with listing. However, it does not explicitly distinguish it from the sibling domains_getWHOISProfileV1, which likely retrieves a single profile. The name includes 'List' but the description could be more precise.

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 provides a basic usage hint ('Use this endpoint to view available contact profiles for domain registration') but no guidance on when to use this tool versus alternatives like domains_getWHOISProfileV1 or domains_createWHOISProfileV1. No exclusions or preprequisites are mentioned.

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