radarr_delete_system_backup

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

The description's warning 'DESTRUCTIVE: this deletes data' merely repeats the existing destructiveHint annotation. It adds no new behavioral context such as irreversibility, cascade effects, or system impact beyond what annotations already convey.

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 is redundant with the annotation. It could be more concise by removing the repetitive warning, leaving only the core action.

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 destructive operation, the description lacks crucial context about permanence, prerequisites, or what backup the id refers to. While an output schema exists, the description still fails to explain the deletion's impact, making it incomplete for effective use.

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 provides no description for 'id' (0% coverage), and the description does not clarify that the id refers to the backup ID or provide any additional meaning. The parameter is left unexplained, forcing the agent to infer its purpose from the tool name.

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 backup') with a specific verb and resource. It distinguishes from siblings like restore_backup and list_system_backup, though the differentiation is implicit rather than explicit.

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 tool versus alternatives, no mention of prerequisites or context in which deletion is appropriate. The description only states the action without any usage direction.

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