Delete Client Contact

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

The description explicitly states permanence and irreversibility ('cannot be undone'), which adds context beyond the annotation destructiveHint=true. It reinforces the destructive nature, though the annotation already covers this.

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 with two short sentences (one per language), no wasted words. It front-loads the core action and key warning.

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 with two parameters, annotations, and output schema, the description is adequate. It covers the destructive nature and permanence, though could mention if this is a soft or hard delete, and any cascading effects.

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%, with bilingual descriptions for both parameters. The tool description adds no extra semantic information about parameters, so 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 clearly states the action ('permanently delete a contact') and the resource ('from a client'), with bilingual text. It distinguishes itself from sibling delete tools by specifying the resource as client contact, but does not explicitly differentiate from similar tools like delete_client_note.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when to use soft-delete or update instead. No prerequisites or conditions are mentioned.

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