cm_copy_sending_domain

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

No annotations provided (readOnlyHint, destructiveHint), so description carries full burden. It states the action but does not disclose side effects, prerequisites, or error behavior. Minimal transparency beyond stating the operation.

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?

Description is a single concise sentence, front-loaded with the main action. No wasted words, but could benefit from brief additional context without becoming verbose.

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?

Description is very brief for a tool with 3 required parameters and no output schema. It omits prerequisites (e.g., source client must have verified domain), success/error indicators, and any constraints. Insufficient for an agent to use reliably without external knowledge.

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 covers 100% of parameters with clear descriptions. Tool description adds no additional meaning beyond what the schema already provides, so baseline score 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?

Description clearly states the action (copy), the resource (verified sending domain), and the scope (from another client to this client). It distinguishes from siblings like add, delete, and authenticate.

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?

Description implies use when copying a verified domain from another client, but does not explicitly state when to use versus alternatives like cm_add_sending_domain or cm_authenticate_sending_domain. No when-not or alternative guidance.

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