delete_relationship

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does mention the important cascade behavior of deleting derived FKs, which is a useful warning. However, it does not disclose irreversibility, permission requirements, error behavior, or what happens to dependent objects beyond the FKs.

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 a single sentence with no wasted words. It is front-loaded with the verb 'Deletes' and the resource, and the parenthetical adds essential behavioral information efficiently.

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 simplicity of the tool but lack of annotations and output schema, this description is too minimal. It does not explain what happens on success, how to find relationshipId, or typical usage scenarios. An agent may not know when to invoke it or what to expect.

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 description coverage is only 50%; the source parameter is well-described but relationshipId has no schema description. The tool description adds no meaning for relationshipId or how to obtain it. With low coverage, the description should have compensated, but it does not.

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 'Deletes a relationship' with a specific verb and resource. The parenthetical '(including derived FKs)' distinguishes it from other relationship tools like upsert_relationship or list_relationships, making the purpose unambiguous.

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 gives no guidance on when to use this tool versus alternatives such as delete_entity or list_relationships. It lacks prerequisites, context, or any explicit 'when to use' or 'when not to use' information.

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