dex_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 of behavioral disclosure. It states the tool is destructive ('permanently delete') and removes all associated data, which is helpful. However, it lacks details on permissions needed, error handling, or confirmation steps, leaving gaps for a mutation tool.

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 concise sentences with no wasted words, front-loading the key action ('permanently delete a contact by ID') and adding necessary detail about data removal. Every sentence earns its place.

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?

Given the tool's destructive nature, no annotations, and no output schema, the description is adequate but incomplete. It covers the core action and scope but lacks details on outcomes (e.g., success response or error cases), which are important for a deletion tool.

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?

The description adds meaning by specifying that the contactId parameter is used to identify the contact to delete, which is useful since schema description coverage is 0%. However, it does not provide format details (e.g., expected ID type or length), so it partially compensates but not fully.

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') and the resource ('a contact by ID'), specifying it removes the contact and all associated data. This distinguishes it from sibling tools like dex_update_contact or dex_merge_contacts by emphasizing irreversible deletion.

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 implies usage by stating it deletes a contact by ID, but does not explicitly guide when to use this versus alternatives like dex_merge_contacts (for combining contacts) or dex_remove_contacts_from_group (for partial removal). It lacks explicit when-not-to-use or prerequisite information.

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