cm_delete_person

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

The annotations already include destructiveHint: true, so the description's addition of a warning emoji adds minimal extra value. No details are given about side effects, reversibility, or required permissions, but the destructive hint covers the core behavior.

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 concise—one sentence with a warning emoji. It is front-loaded and contains no unnecessary words, making it easy to scan.

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?

While the tool is simple, the description provides no context about return values, idempotency, or what happens after deletion (e.g., cascading effects). Given the lack of an output schema, more detail would be helpful for complete understanding.

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?

Input schema has 100% description coverage for its two parameters (email and clientId). The tool description does not add any further parameter information, so it meets the baseline expectation without enhancement.

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' and the resource 'person from a client account', making the tool's purpose immediately clear. However, it lacks specificity about the scope (e.g., permanent removal) and does not differentiate from similar tools like cm_delete_subscriber.

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 provided on when to use this tool versus alternatives like cm_delete_subscriber or cm_remove_person (if exist). The description does not mention prerequisites, restrictions, or conditions for safe usage.

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