Delete Contact

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

The description repeats the destructive nature already indicated by the destructiveHint annotation and adds no additional behavioral context. It does not disclose whether deletion is permanent, reversible, or cascades to related data, missing an opportunity to inform the agent of critical side effects.

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 extremely concise with no filler words. It is appropriately sized for a simple delete operation, though it may be slightly under-specified for a complex use case.

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 tool with a single parameter, a destructive hint, and no output schema, the description is minimally sufficient. However, it lacks context about what 'delete' entails (e.g., permanence, impact on related data) and any prerequisites, making it only partially complete for an agent's decision-making.

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% and the single parameter 'uuid' is described as 'Contact UUID'. The description itself provides no additional semantic value beyond the schema, so the baseline of 3 is appropriate.

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 'Delete a contact.' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes from sibling tools like reach_contacts_list and reach_contacts_create, though it could be slightly more explicit about the unique identifier (UUID) used to select the contact.

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 guidance is provided on when to use this tool versus alternatives, nor any mention of prerequisites, consequences, or edge cases. The description is purely functional and lacks contextual direction for an agent deciding between this and other contact-related tools.

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