radarr_delete_tag

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond repeating 'Delete' — critically, it does not say whether the tag is stripped from all associated movies, whether it can be recovered, or what a failure looks like. For a destructive mutation, that is a real gap.

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?

One efficient, front-loaded sentence with no waste. It is appropriately sized but borders on under-specification given the operation is destructive.

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?

A destructive, open-world mutation with no output schema and no annotation-independent detail leaves the agent without knowledge of side effects, confirmation requirements, or failure modes. The description is complete only in the narrowest sense of naming the operation.

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 100%, and the schema itself documents 'Tag ID (from radarr_get_tags)', which fully covers the single parameter. The description contributes no additional meaning, so baseline 3 applies.

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?

Specific verb and resource ('Delete a Radarr tag by ID') — an agent can immediately distinguish it from radarr_create_tag and radarr_update_tag in the sibling list. The 'by ID' qualifier identifies the keyed operation, though it does not explicitly name the alternative tools.

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?

No guidance on when to use this versus radarr_update_tag or when deletion is appropriate. There is no mention of prerequisites (fetching the ID via radarr_get_tags is only in the schema) or of any warning about irreversible removal.

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