Delete a profile contact

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

The description adds meaningful behavioral context beyond the annotations: the deletion is permanent AND cascades to custom field values and tag assignments. This tells the agent what collateral effects occur. It does not contradict the destructiveHint or idempotentHint annotations.

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 concise sentences with no filler. The core destructive action is front-loaded, and the second sentence provides the most valuable additional behavioral detail without becoming verbose.

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 two-parameter delete operation, the description, schema, and annotations together provide sufficient information: required UUIDs, destructive safety profile, idempotency, and cascade behavior. It only lacks explicit sibling differentiation, but that is not essential to invoking this tool 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?

Schema coverage is 100%, so both parameters are already documented in the input schema. The description reinforces that one parameter identifies a contact and the other a profile, but it adds no deeper semantic detail such as formats, sources, or validation rules.

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 from a profile. The phrase 'from a profile' distinguishes this from sibling tools like reach_deleteAContactV1, though it does not explicitly name or contrast the alternative.

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?

There is no guidance on when to use this tool versus reach_deleteAContactV1 or other contact-related deletion tools. The description implies this is profile-scoped contact deletion, but it never states when this is the right choice or when another sibling would be appropriate.

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