deleteTagRelationship

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds critical context: 'Permanently delete', 'cannot be undone via API', 'No soft-delete... records not recoverable', and specifies the return format. No contradiction with annotations.

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 concise (~100 words), well-structured with bolded headings ('Use when:', 'Required:', 'See also:', 'Destructive:', 'Returns:'), and front-loaded with the core action.

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 tool with one parameter and no output schema, the description covers behavior, prerequisites, return value, and potential side effects (member_tags CSV). It is complete and actionable.

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 0% for description, and the description only says 'Required: `id`.' It does not explain what the ID represents (likely a tag relationship ID) or how to obtain it. The description adds minimal value beyond the schema.

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 'Delete a tag relationship - Permanently delete a tagrelationship record by ID.' It uses a specific verb and resource, and distinguishes from sibling 'updateTagRelationship' by noting the difference (modify without removing).

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?

Explicit 'Use when: detaching a tag from a record' and a note about updating member_tags CSV separately. Also advises confirming intent before bulk use and references 'See also: updateTagRelationship (modify without removing)' for alternatives.

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