radarr_delete_tag

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description adds 'DESTRUCTIVE: this deletes data,' which essentially restates the annotation without providing additional behavioral context (e.g., irreversibility, cascading effects on movies using the tag). 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 very short and front-loaded with the core action. The second sentence, 'DESTRUCTIVE: this deletes data,' is somewhat redundant with the annotations, but the overall length is appropriate and it does not include unnecessary detail.

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 operation (delete by ID) and the presence of destructive annotations and an output schema, the description is minimally adequate. However, it does not clarify what `id` refers to, whether the deletion is permanent, or any side effects on associated resources, which could be important for the agent.

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 schema has one parameter `id` (integer) with no description, and schema description coverage is 0%. The description does not compensate by explaining that `id` refers to the tag ID or provide any additional parameter context. The meaning is inferable from the tool name but the description adds no semantic value.

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 action ('Delete tags') with a specific verb and resource. It distinguishes itself from sibling tag operations like radarr_list_tag, radarr_create_tag, radarr_update_tag, and radarr_get_tag by unambiguously indicating deletion.

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 clearly indicates the tool is for deleting tags, which is a distinct action among the sibling tools. However, it does not provide explicit guidance on when not to use it (e.g., if a tag is in use) or mention any prerequisites, but the usage context is clear enough.

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