reach_deleteAContactV1

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

The description discloses that the action is permanent and destructive ('permanently removes'), which is critical behavioral information. However, with no annotations provided, the description carries the full burden. It lacks details on potential side effects, authentication requirements, rate limits, or error states.

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 two sentences. The first sentence immediately states the action, and the second adds important context (permanence and system). No extraneous information is included.

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 one parameter and no output schema, the description is adequate but not fully complete. It doesn't mention that the action is irreversible (beyond 'permanently removes' which is good), nor does it cover expected responses or error conditions. Given the tool's simplicity, it meets minimum viability.

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 schema covers the single parameter with description 'UUID of the contact to delete'. The description merely echoes this ('specified UUID'), adding no additional semantic meaning. Given 100% schema coverage, a score 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 clearly states the action ('Delete a contact') and specifies the required identifier ('specified UUID'). It distinguishes itself from sibling tools like 'reach_createANewContactV1' (create) and 'reach_listContactsV1' (list) by focusing on deletion. The additional detail 'permanently removes' reinforces the purpose.

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 for deleting a contact but does not explicitly state when to use it versus alternatives or provide exclusions. There are no sibling tools for deleting contacts, but no guidance on prerequisites or conditions (e.g., contact must exist) is given.

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