delete_contact

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

With no annotations, the description alone must carry the full behavioral burden for a destructive operation, but it only repeats the action verb. It does not say whether deletion is permanent or soft, what happens to associated documents or attachments, or whether confirmation is required. Because it does not contradict anything, this is 2 rather than 1.

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 a single short phrase with the action front-loaded and no wasted words. It is efficient, though its brevity leaves required context uncovered rather than including too much.

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 destructive mutation with no annotations and no output schema, the description is too thin. It omits permission requirements, irreversibility, side effects on related records, and the expected response. This is not enough for an agent to invoke the tool safely.

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 coverage is 100%, so the single contactId parameter is already fully documented. The description adds nothing about the ID format or its source. A baseline of 3 applies because the schema does the documentation work.

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 states a specific verb and resource: "Delete a contact." This is distinct from siblings like delete_contact_group or delete_product because it names the target resource explicitly. It does not, however, explain how it differs from those adjacent delete tools, which keeps it from a 5.

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?

It gives no guidance on when to use this tool, what prerequisites apply (such as the contact existing), or what alternatives exist. There is no warning that deletion is permanent, and no instruction on verifying the contact ID first.

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