Set Email Protection

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

Annotations already provide openWorldHint, idempotentHint, and destructiveHint. The description adds important behavioral detail: disabling exposes the email and increases spam/phishing risk, and advises user confirmation. This goes beyond annotations, though it does not mention reversibility or rate limits.

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 three sentences, clear and front-loaded with the action. The warning is important but placed at the end. It is concise and well-structured, with no unnecessary words.

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 toggle tool with two parameters and no output schema, the description covers the purpose, effect, and a critical warning about disabling. It could mention prerequisites (e.g., domain must be registered) but is fairly complete.

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 for both parameters. The description references the parameters (domain and contactForm) but does not add new semantics beyond what the schema already provides.

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 toggles the contact form display for WHOIS, specifying the verb 'toggle' and resource 'contact form display for domain WHOIS'. It distinguishes from sibling tools like set_privacy_level by focusing on WHOIS contact form.

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 the effect of enabling (shows contact form, protects email) and disabling (exposes email, risk of spam/phishing), and instructs to confirm with user before disabling. This provides clear context for when to use, though it does not explicitly state when not to use or compare to alternatives.

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