radarr_delete_exclusions

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

The destructiveHint annotation already signals destructiveness. The description adds 'DESTRUCTIVE: this deletes data,' which restates the annotation but does not provide additional behavioral context such as irreversibility, permissions required, or side effects on related records.

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 short and front-loaded, but the second sentence ('DESTRUCTIVE: this deletes data') is largely redundant with the destructiveHint annotation. It could be trimmed to a single sentence without losing meaning.

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 operation, the description is minimal. It lacks details on what the id refers to, whether the deletion is permanent, and any consequences. The output schema exists but the description does not help an agent understand the operation beyond the basic action.

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 'id' integer parameter with no description and the description does not explain its meaning. While the tool name implies the id refers to an exclusion, the description fails to clarify this explicitly, and with 0% schema coverage, it needed to compensate.

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') and the target resource ('import list exclusions'), using a specific verb and noun. It distinguishes from siblings like radarr_bulk_delete_exclusions by indicating a single-item delete.

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 is given about when to use this tool versus alternatives such as bulk delete or update. It simply states what it does without context on prerequisites or preferred scenarios.

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