conduyt_delete_contact

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

With no annotations provided, the description carries the full burden and does so well: it discloses that this is a soft-delete, that the row is retained for audit while disappearing from lists/searches, that deals are unaffected, and that there is no API-level undo. These are exactly the behavioral facts an agent needs before invoking a destructive-looking 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?

Two tight sentences with zero filler. The purpose and the critical caveat (soft-delete/irreversibility) are front-loaded, and every clause adds decision-relevant information.

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 delete tool with no output schema and no annotations, the description covers what the agent needs: what is deleted, what survives, what side effects do not occur (deals), and that reversal is not possible via the API. Nothing material is missing.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents the UUID fully. The description adds only the phrase "by UUID", restating what the schema says. Baseline 3 is appropriate when the schema does all the heavy lifting.

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?

States a specific verb and resource ("Delete a contact by UUID") and immediately clarifies the non-obvious semantics of the operation (soft-delete, row retained, deals unaffected). It does not explicitly distinguish itself from siblings like conduyt_bulk_delete_contacts or conduyt_forget_contact, but the singular/UUID framing makes the scope reasonably clear.

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?

Gives an explicit use case ("clean up test or duplicate contacts") and a strong caution ("no undelete endpoint, so treat it as irreversible via the API"). It stops short of naming the batch alternative for deleting many contacts at once, which is the main routing decision an agent faces here.

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