reach_deleteAProfileContactV1

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

With no annotations provided, the description carries full burden. It explicitly states the operation is 'Permanently delete' and discloses that the contact is 'removed together with its custom field values and tag assignments.' This provides valuable behavioral context for a destructive operation, though it omits details like permissions or response.

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 two short sentences, front-loaded with the main action and followed by a crucial consequence. Every word earns its place; no redundant or vague language.

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, the description sufficiently covers the action and its scope (profile, custom fields, tags). It does not explain return values or permission requirements, but these are less critical when no output schema is present and the operation is destructive. It could be more explicit about the relationship between profileUuid and contactUuid.

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 descriptions are present for both parameters but are tautological ('Profile uuid parameter', 'Contact uuid parameter'). The tool description adds no additional meaning about the parameters, so it does not exceed the baseline set by the high schema coverage. Both parameter names are self-explanatory, offering minimal added value.

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.' This specifically identifies the resource (contact within a profile) and differentiates it from sibling tools like reach_deleteAContactV1 (delete any contact) and reach_deleteAContactFieldV1 (delete a contact field).

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention when to choose this over reach_deleteAContactV1 or other delete-related tools, nor does it provide exclusions or prerequisites. The intended context must be inferred from the name and description alone.

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