deleteTagRelationship

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

Annotations already provide destructiveHint and readOnlyHint, but the description adds valuable context: 'Destructive - cannot be undone via API', 'No soft-delete via API - records removed are not recoverable', and the return format. Could mention idempotency implications, but overall strong.

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 well-structured with clear sections: overview, use when, required, see also, destructive warning, returns. Each sentence is necessary and adds value. Very concise.

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 annotations, the description covers all necessary aspects: purpose, usage context, parameter requirement, destructive behavior, return format. It is complete and provides adequate guidance.

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?

Only one parameter 'id' (integer, required). Schema description coverage is 0%, but the description specifies 'Required: id.' However, it does not clarify what the ID represents (e.g., tagrelationship record ID), though it's implied. Minimal addition beyond 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 the tool's purpose: 'Delete a tag relationship - Permanently delete a tagrelationship record by ID.' This distinguishes it from siblings like 'updateTagRelationship' (modify without removing) and 'createTagRelationship'.

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?

Explicitly states when to use: 'Use when: detaching a tag from a record.' Provides a note about CSV member_tags, refers to 'updateTagRelationship' as an alternative, and warns about destructive nature with confirmation advice.

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