Get WHOIS Profiles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely restates the title ('List all WHOIS profiles') without adding context on pagination, rate limits, empty results, or how profiles relate to domain purchases, providing minimal insight beyond what the tool name already conveys.

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 a single, tight sentence with no filler or redundant elaboration. Every word earns its place and the primary action ('List') is front-loaded, making it maximally concise.

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 list operation with no output schema and no annotations, the description is adequate but minimal. It could improve by noting the relationship to sibling tools, such as clarifying that domains_get_whois_profile retrieves a single profile, but the low complexity of the tool keeps this gap modest.

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 has zero properties, and the schema already makes clear that no parameters are required. With 0 parameters, the baseline of 4 applies, as the description has no additional parameter semantics to explain.

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 'List all WHOIS profiles' uses a specific verb ('List') and a clear resource ('WHOIS profiles'), making the core operation unambiguous. However, it does not explicitly differentiate from the sibling tool domains_get_whois_profile, relying on the singular/plural contrast in tool names to convey the distinction.

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 no guidance on when to choose this tool over its siblings. It does not mention that domains_get_whois_profile should be used for retrieving a single profile, nor does it explain the relationship to domains_get_whois_profile_usage, leaving the agent to infer the appropriate context solely from the tool name.

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