delete_verified_domain

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

Annotations mark destructiveHint=true and idempotentHint=true. Description adds context: 'Irreversible', 'Authenticated via API key', 'Max 10 concurrent requests', and 'Respects read-only and dry-run modes.' No contradictions.

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 well-structured: opening sentence, then emphasis on irreversibility, usage note, authentication/limits, and parameter definitions. Every sentence adds value with no redundancy.

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?

Given the tool's complexity (2 params, destructive action), the description covers purpose, side effects, prerequisites, parameter details, authentication, rate limits, and return format (via output schema). It is complete and actionable.

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 0%, but description explains both parameters fully: domain_name with example and source (list_verified_domains), account with example and configuration reference (list_accounts). This adds crucial 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 clearly states the action: 'Delete a verified sending domain from the account permanently.' It identifies the specific resource (verified sending domain) and uses a strong verb. It distinguishes from sibling tools like list_verified_domains, create_verified_domain, and verify_verified_domain.

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?

Explicitly tells when to use: 'Use list_verified_domains to find domain names first.' It also mentions irreversibility and that deletion prevents reuse until re-verified. Provides guidance on the optional account parameter and refers to list_accounts.

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