delete_verified_domain

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Remove' implies a destructive action, but it does not state whether the deletion is permanent, irreversible, subject to restrictions, or has side effects on associated campaigns or automations. It adds no context beyond what the tool name already implies.

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 extremely brief (one sentence, five words), but it is under-specified. It offers no useful information beyond the tool name, making it a tautology rather than a concise, informative description.

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 destructive mutation tool with no annotations and no output schema, the description is too sparse. It fails to explain the consequences (permanence, prerequisites, or effects on related data) or the response behavior. Even with sibling context, it remains incomplete.

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% — the only parameter 'domain' has a clear description ('The domain name to remove'). The tool description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 'Remove a verified domain' clearly identifies the action (remove) and resource (verified domain). It is distinct from sibling tools like list_verified_domains, get_verified_domain, create_verified_domain, and send_domain_verification_email.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the domain must exist), exclusions (e.g., cannot be removed if in use), or alternatives (e.g., send_domain_verification_email for resending verification). The description simply restates the function.

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