Get WHOIS Profile

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

With no annotations provided, the description relies on 'Get' to imply a read-only operation, but it discloses no other behavioral traits such as return format, error conditions, or whether the profile includes detailed data. This is a minimal disclosure for a tool with zero 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 a single front-loaded sentence with no fluff. It is efficient but lacks helpful contextual details that could have been included without much extra length.

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?

With no output schema and no annotations, the description should clarify what a WHOIS profile contains and what a successful response looks like. It does neither, making the tool incomplete for an agent that needs to interpret results or handle errors correctly.

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 only parameter 'whois_id' is documented as 'WHOIS profile ID'. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Get a specific WHOIS profile' uses a clear verb ('Get') and identifies the resource ('WHOIS profile'). The word 'specific' distinguishes it from the sibling list tool 'domains_get_whois_profiles', though it does not explicitly name alternatives.

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 use this tool versus alternatives like domains_get_whois_profiles or domains_get_whois_profile_usage. It does not state any prerequisites or context, leaving the AI agent to infer usage from the terse text.

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