Permanently delete a relationship from a DataForge project version by specifying project, version, and relationship IDs. Removes the specified relationship to clean up your data model.
PERMANENTLY DELETES DATA IN DATAFORGE. Delete a relationship.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | DataForge project id | |
| version_id | Yes | Project version id | |
| relationship_id | Yes |
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark destructiveHint=true and idempotentHint=true. The description adds the explicit 'PERMANENTLY DELETES DATA' warning, which reinforces irreversibility, but it provides no detail about cascading effects or whether any confirmation is needed.
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 and contains no filler. The permanence warning is front-loaded and directly supports safe usage.
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 three-parameter delete operation, the annotations and description convey the essential destructive nature. Yet the absence of usage guidance and any mention of preconditions or post-conditions leaves the context only partially complete.
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?
With 67% schema coverage, project_id and version_id are documented, and 'Delete a relationship' makes the role of relationship_id clear. However, the description adds no real semantic value beyond the schema and does not compensate for relationship_id's missing schema description.
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 states a specific verb and resource: 'Delete a relationship.' The all-caps warning clarifies this is a permanent deletion, and naming 'relationship' distinguishes it from sibling delete tools such as df_delete_version or df_delete_measure.
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?
There is no guidance about when to use this tool versus alternatives. It does not mention verifying the relationship first with df_get_relationship, nor does it distinguish deletion from creation/listing operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.