send_domain_verification_email

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

With no annotations, the description carries the full burden of behavioral disclosure but only states the action. It doesn't mention whether the domain must exist, whether it resets verification state, rate limits, or what happens if already verified. This leaves the agent without critical context.

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 of seven words with no redundant content. 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?

This is a simple tool (1 param, no output schema), but with no annotations, the description doesn't disclose preconditions, side effects, or return value. The brief description leaves important operational details unsaid, especially given the surrounding domain verification workflow.

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 schema provides 100% coverage with a description for 'domain' ('The domain name'), so the baseline is 3. The tool description's 'for a domain' adds no additional meaning beyond the schema.

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 uses a specific verb ('Resend') with a clear resource ('verification email') and target ('a domain'), distinguishing it from sibling domain tools like create_verified_domain or list_verified_domains. It is unambiguous and immediately conveys the action.

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 explicit guidance on when to use this tool versus alternatives like create_verified_domain or list_verified_domains. The verb 'Resend' implies a prior verification email, but this is not stated as a precondition or compared to other tools.

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