Delete Relationship

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

With no annotations, the description carries the burden of behavioral disclosure. It goes beyond a simple 'delete' by warning that the action permanently removes the relationship from both contact records, which is key side-effect information. It does not detail error handling or return values, but for a single-parameter delete operation this is reasonably transparent.

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 sentences, front-loading the core purpose and following with a clear warning. Every sentence contributes meaningful information with zero waste.

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 low complexity (one required parameter, no output schema, no annotations), the description sufficiently covers the essential action and its permanent side effect. It could mention return behavior or error cases, but for a simple delete tool these are not critical gaps.

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 input schema covers 100% of the parameters, with relationship_id already described as 'The RelationshipId to delete'. The description adds no additional parameter meaning beyond what the schema provides, so a baseline 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 specific action ('Delete') on the resource ('relationship between two contacts'), distinguishing it from sibling tools like edit_relationship (modify) and get_relationship (read). The additional warning reinforces the specific nature of the operation.

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 provides clear context that this tool permanently deletes the relationship, signaling that it should only be used when irreversibility is intended. However, it does not explicitly mention alternatives (e.g., edit_relationship) or when not to use this tool, leaving the guidance implied rather than fully explicit.

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