Set WHOIS Privacy Level

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

Annotations indicate idempotentHint=true and destructiveHint=false, but the description adds critical context: setting to 'public' exposes personal contact info which cannot be uncached once indexed. This goes beyond annotations to warn about irreversible privacy implications, fully informing the agent.

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?

Three sentences plus a warning: every sentence serves a purpose. The warning is critical and clearly separated. No fluff, perfectly front-loaded with the core action, then details and caution. Highly efficient.

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, the description fully covers input behavior, options, and risks. It explains what the tool does, the two level values, the consent requirement, and the irreversible nature of public exposure. No gaps remain for an agent to misuse the tool.

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 descriptions, so baseline is 3. The description adds extra context for the 'level' parameter by explaining consequences of 'public', and reinforces the 'userConsent' requirement. This adds meaningful semantic value beyond schema, earning a 4.

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 sets WHOIS privacy level for a domain, explicitly defining 'high' and 'public' options. This verb+resource combination is distinct among sibling tools, which are focused on domain management, DNS, contacts, etc., making the purpose unambiguous.

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 explains when to use each privacy level and strongly advises confirming with the user before setting to 'public'. While it doesn't explicitly list alternatives (there are none), it provides clear context for safe usage, warranting a 4.

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