Delete a contact

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

Beyond the destructiveHint annotation, the description discloses exactly what happens: deletion is permanent, past appointments are retained, and the contact record plus form answers are removed. This gives the agent clear expectations about side effects and data preservation.

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?

Two short sentences with the primary action front-loaded. Every clause adds meaningful information: permanence, retention of appointments, and removal of contact record and form answers. There is no filler.

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 single-parameter destructive action with an output schema and destructiveHint annotation, the description fully covers what is deleted, what persists, and the permanent nature of the operation. No critical context is missing for an agent to invoke it correctly.

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?

With 0% schema description coverage, the description needed to explain contactId, but it never explicitly references the parameter. The agent must infer from the property name and the phrase 'a CRM contact' that contactId identifies which contact to delete. This is minimal compensation for a parameter with no schema-level documentation.

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 uses a specific action verb ('delete'), names the exact resource ('CRM contact'), and clarifies the action is permanent. This clearly distinguishes it from sibling delete tools that target other entity types such as knowledge documents, meeting types, routing forms, or webhooks.

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 gives no explicit guidance on when to use this tool instead of alternatives like update_contact, create_contact, or search_contacts. There are no prerequisites, no confirmation steps, and no mention of when deletion is appropriate versus other contact operations.

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