list_backups

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'List' implies a read-only operation, and the explicit note about running the Backup command to create a new backup clarifies that this tool does not create backups. This is useful behavioral context beyond the bare resource name.

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?

Two short sentences with no filler. The first sentence states the core purpose, and the second provides a relevant pointer to the companion command. Every word earns its place.

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 zero-parameter list operation with no output schema and no annotations, the description covers the essential details: what is listed, what fields are returned, and how to perform the related create action. It could be slightly more explicit about the 'Backup command' being invoked through a sibling tool like run_command, but this is a minor gap.

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, so there is nothing to document. The baseline for 0 parameters is 4, and the description adds value by naming the output attributes (type, size, date), which helps the agent understand the returned data even though no output schema exists.

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 states a specific verb ('List'), a specific resource ('database backups Sonarr has taken'), and the output fields ('type, size and date'). This clearly distinguishes it from sibling list tools like list_series or list_episodes, which target different resources.

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 explicitly routes the creation action elsewhere: 'Run the Backup command to create a new one.' This tells the agent when not to use this tool. It doesn't explicitly contrast with other list tools, but the resource-specific language makes the intended use clear.

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