radarr_delete_metadata

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

The description explicitly states 'DESTRUCTIVE: this deletes data', which aligns with the destructiveHint=true annotation but adds no new behavioral information beyond what the annotation already provides. No additional context is given about irreversibility, cascading effects, or required permissions.

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 two short sentences that are front-loaded with the primary purpose and include a brief warning. It is appropriately sized for a simple delete operation without extraneous text.

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 deletion tool, the description covers the basic purpose and destructiveness, but it leaves gaps: no mention of what the id parameter means, no usage conditions, and no reference to alternatives. Given the existing annotations and output schema, the description is minimally sufficient but not complete.

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 input schema has one required parameter 'id' with no description, and the description does not explain that 'id' refers to the metadata provider ID or how to obtain it. With 0% schema description coverage, the description fails to compensate, leaving the parameter's semantics implicit at best.

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 uses the specific verb 'Delete' with the resource 'metadata providers', clearly distinguishing this from sibling tools like radarr_get_metadata, radarr_update_metadata, and radarr_list_metadata. The operation is unambiguous and matches the tool name.

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 provides no guidance on when to use this tool instead of alternatives such as radarr_update_metadata or radarr_disable_metadata. It lacks any context about prerequisites, such as needing the metadata provider ID, or when deletion is appropriate versus other actions.

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