ss_domain_email_protection

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

No annotations are provided, and the description simply states 'Toggle... for a domain'. It does not disclose whether the change is immediate, requires any permissions, affects other settings, or is reversible. For a mutation tool, this minimal disclosure leaves significant behavioral gaps.

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 sentence that is clear, front-loaded, and contains no unnecessary words. Every word earns its place.

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, the description is adequate but lacks behavioral context such as whether the action is synchronous, if any prerequisites exist, or what the return value indicates. Without an output schema, the description could provide more completeness about the effect and confirmation.

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?

Both parameters have descriptions in the input schema (domain: 'Domain name', contactForm: 'true to show contact form, false to hide'). The description adds no additional meaning beyond the schema. With 100% schema coverage, baseline is 3, and the description does not enhance parameter understanding.

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 email protection (contact form link in WHOIS) for a domain. It uses a specific verb (toggle) and resource (email protection), and clarifies what email protection means. This distinguishes it from sibling tools like ss_domain_privacy and ss_domain_contacts.

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 implies usage for enabling/disabling the contact form link, but provides no explicit guidance on when to use this tool versus alternatives such as ss_domain_privacy or ss_domain_contacts. No when-not-to-use or comparison to siblings is given.

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