radarr_list_system_backup

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

The annotation readOnlyHint: true already declares the safe read-only nature, so the description adds no extra behavioral context. It does not mention return format, pagination, or any side effects, but the readOnly annotation covers the main safety aspect.

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 extremely concise with no filler words or repetition. It is front-loaded and effectively communicates the tool's purpose in two words, earning its place without excess.

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 tool's simplicity, the presence of an output schema, and the readOnly annotation, the description is sufficient for an agent to understand the basic operation. However, it could benefit from a slight expansion to clarify that it lists system backups, which is implied by the tool name.

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 tool has zero parameters, and the schema description coverage is 100%. Since there are no parameters to explain, the baseline is 4, and the description is not required to add parameter details. No gaps exist.

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 'List backup.' clearly identifies the action (list) and resource (backup), distinguishing it from sibling tools like radarr_restore_backup and radarr_delete_system_backup. It is concise and unambiguous, though it could be more specific by stating 'system backup'.

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 versus alternatives, and no exclusions or prerequisites are mentioned. It is a simple command, but there is no explicit context or comparison with other list operations.

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