cm_delete_sending_domain

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

The destructive hint annotation already indicates the operation is destructive. The description adds a warning emoji (⚠️) for emphasis but does not disclose additional behavioral details such as irreversibility or impact on active usage.

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?

Single sentence with a front-loaded warning emoji. Concise and to the point with no extraneous 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 delete operation, the description is adequate in stating the primary action. However, it lacks information about consequences (e.g., whether deletion requires domain to be unused) and return value, which could help an agent handle errors.

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 description coverage is 100%, so the description does not need to add parameter details. It correctly omits redundant parameter elaboration, though it could optionally explain the relationship between clientId and Domain.

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?

Description clearly states the action (remove) and resource (sending domain), and specifies the scope (from a client). It differentiates from sibling tools like cm_add_sending_domain and cm_get_sending_domains.

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 on when to use this tool versus alternatives like cm_authenticate_sending_domain or cm_copy_sending_domain. Missing context such as prerequisites or when deletion is appropriate.

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